You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Phabricator (JIRA)" <ji...@apache.org> on 2013/01/08 10:38:14 UTC

[jira] [Commented] (HIVE-3849) Aliased column in where clause for multi-groupby single reducer cannot be resolved

    [ https://issues.apache.org/jira/browse/HIVE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546736#comment-13546736 ] 

Phabricator commented on HIVE-3849:
-----------------------------------

njain has commented on the revision "HIVE-3849 [jira] Columns are not extracted for multi-groupby single reducer case somtimes".

INLINE COMMENTS
  ql/src/test/queries/clientpositive/groupby_multi_single_reducer3.q:5 Why not have the same test with hive.optimize.ppd set to true also ?
  ql/src/test/queries/clientpositive/groupby_multi_single_reducer3.q:7 Can you add a test where there is an expression on the where clause ?

  from src
  insert overwrite table e1
  select value, count(*)
  where src.key + src.key = 100 or src.key + 7 = 207 or src.key = 300
  group by value
  .....


REVISION DETAIL
  https://reviews.facebook.net/D7713

To: JIRA, navis
Cc: njain

                
> Aliased column in where clause for multi-groupby single reducer cannot be resolved
> ----------------------------------------------------------------------------------
>
>                 Key: HIVE-3849
>                 URL: https://issues.apache.org/jira/browse/HIVE-3849
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Minor
>         Attachments: HIVE-3849.D7713.1.patch, HIVE-3849.D7713.2.patch, HIVE-3849.D7713.3.patch
>
>
> Verifying HIVE-3847, I've found an exception is thrown before meeting the error situation described in it. Something like, 
> FAILED: SemanticException [Error 10025]: Line 40:6 Expression not in GROUP BY key 'crit5'

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