[
https://issues.jboss.org/browse/TEIID-2675?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2675.
-----------------------------------
Resolution: Done
Took the approach of just tracking if a user defined aggregate has been found and then
doing a focused rewrite after resolving. All downstream logic is unaffected and we
don't have to retrofit expression mapping into resolving in general.
Ensure that user defined aggregate functions don't require
additional syntax
----------------------------------------------------------------------------
Key: TEIID-2675
URL:
https://issues.jboss.org/browse/TEIID-2675
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.6
User defined aggregates require additional syntax if they look like simple functions.
This is not ideal, but was not addressed initially due to the lack of effective rewrite
support in the resolver and all of the logic that is built around the differentiation
between Function and AggregateSymbol classes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira