[teiid-issues] [JBoss JIRA] (TEIID-2801) HIVE2: HAVING specified without GROUP BY

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935468#comment-12935468 ] 

Steven Hawkins commented on TEIID-2801:
---------------------------------------

There are two parts here.  The first is to double check the aggregate pushdown logic to see if we really need the null check in this and similar cases.  The other is that we don't currently have a way for capabilities to convey that having requires group by.
                
> HIVE2:  HAVING specified without GROUP BY
> -----------------------------------------
>
>                 Key: TEIID-2801
>                 URL: https://issues.jboss.org/browse/TEIID-2801
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 8.6
>         Environment: Teiid with HIVE1 and HIVE2
>            Reporter: Ivan Chan
>            Assignee: Steven Hawkins
>              Labels: teiid
>
> If SQL contains HAVING, with group by.
> HIVE2 will throw the following exception: 
> HAVING specified without GROUP BY, errorCode:40000, SQLState:42000)
>         at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494)
>         at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480)
>         at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430)
>         at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
>         at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116)
>         at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103)
>         at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175)

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