[ 
https://issues.apache.org/jira/browse/HIVE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phabricator updated HIVE-3849:
------------------------------

    Attachment: HIVE-3849.D7713.5.patch

navis updated the revision "HIVE-3849 [jira] Columns are not extracted for 
multi-groupby single reducer case somtimes".
Reviewers: JIRA

  Fixed test result which is affected by HIVE-3699


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

AFFECTED FILES
  ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
  ql/src/java/org/apache/hadoop/hive/ql/parse/TypeCheckProcFactory.java
  ql/src/test/queries/clientpositive/groupby_multi_insert_common_distinct.q
  ql/src/test/queries/clientpositive/groupby_mutli_insert_common_distinct.q
  ql/src/test/queries/clientpositive/groupby_multi_single_reducer3.q
  ql/src/test/results/clientpositive/groupby_multi_insert_common_distinct.q.out
  ql/src/test/results/clientpositive/groupby_mutli_insert_common_distinct.q.out
  ql/src/test/results/clientpositive/groupby_multi_single_reducer3.q.out

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, HIVE-3849.D7713.4.patch, HIVE-3849.D7713.5.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

Reply via email to