[teiid-issues] [JBoss JIRA] (TEIID-2568) Order by is omitted when projection is raised above ordering with grouping

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins closed TEIID-2568.
---------------------------------


    
> Order by is omitted when projection is raised above ordering with grouping
> --------------------------------------------------------------------------
>
>                 Key: TEIID-2568
>                 URL: https://issues.jboss.org/browse/TEIID-2568
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 7.7
>         Environment: Windows and teiid 8.1
>            Reporter: Rakesh Balguri
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 8.4.1, 8.5, 7.7.8
>
>         Attachments: Query_Plan_SQL_1.txt, Query_Plan_SQL_2.txt
>
>
> I have a SQL which contain constants in the Select clause and also it contains Group By, Order By and Limit clauses in the SQL.
> When I execute the SQL, the Order By clause is not being pushed to the underlying translator. My translator doesn't support "SelectExpressions" i.e. supportsSelectExpression() returns false.
> When I remove the constant from the Select clause then the Order By is pushed to the translator.
>  
> Is this a bug in Teiid's query Optimizer?
>  
> The following are the sample queries and attached are the Query Plans for both the SQL's.
>  
> Query1: This SQL doesn't push the Order By clause to the translator.
>  
> SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT, 'SECURITY.BASERULE' AS "__objecttype__" FROM
> SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22
>  
> Query2: This SQL pushes the Order By to the translator.
>  
> SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT FROM
> SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22

--
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