[
https://issues.jboss.org/browse/TEIID-2487?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2487:
---------------------------------------
Also do not understand why the query engine pushed the aggregate is
being pushed, possibly due to "supportsAggregatesSum" is turned on
I don't follow you. supportsAggregateSum (and group by) has to be turned on or you
wouldn't have it pushed down. The issue is alias generation is expecting all select
clause expressions to be column references if supportsSelectExpression is turned off -
this doesn't account for aggregates in the event that aggregate support is also
enabled (for planning purposes grouping produces internal column references that are later
prior to alias generation are substituted for their aggregate expression form).
Wrong aliasing when "supportsSelectExpression" is false in
translator capabilities
----------------------------------------------------------------------------------
Key: TEIID-2487
URL:
https://issues.jboss.org/browse/TEIID-2487
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
When "supportsSelectExpression" is false, in the translator capabilities and
user submits a query like
{code}
select sum (intnum) as "sum" from smalla group by intkey order by
"sum"
{code}
the pushdown command at the translator is
{code}
SELECT SUM(SMALLA.INTNUM) FROM SMALLA GROUP BY SMALLA.INTKEY ORDER BY c_0
{code}
The alias in the ORDER BY is wrong. Also do not understand why the query engine pushed
the aggregate is being pushed, possibly due to "supportsAggregatesSum" is turned
on.
--
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