hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Thusoo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-25) [Hive] cluster by does not work with column aliasing
Date Tue, 13 Jan 2009 22:44:59 GMT

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

Ashish Thusoo commented on HIVE-25:

In Hive.g the change to the rule for columnNameOrder will also change the ddl (the tablebuckets
rule) and there we clearly do not have a notion of tableColumn as there is no table alias.

We need to think a bit to see if we really want to lift this restriction. The reason it was
modeled like this was because of the transform operator. Basically, the cluster by clause
addresses the alias list instead of the select expressions. There are no tangible select expressions
in the transform case. 


> [Hive] cluster by does not work with column aliasing
> ----------------------------------------------------
>                 Key: HIVE-25
>                 URL: https://issues.apache.org/jira/browse/HIVE-25
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Namit Jain
>            Assignee: Prasad Chakka
>            Priority: Critical
>             Fix For: 0.2.0
>         Attachments: hive-25-code-changes.patch, hive-25.patch
>                     SELECT b.*  
>                     FROM                                                 
>                     (                                                    
>                       SELECT x.col1, x.col2
>                       FROM tmp x              
>                       WHERE x.col2= 10
>                       CLUSTER BY col2                                  
>                     ) b"
> The above query works, but if I change the cluster by to:
> CLUSTER BY x.col2, 
> it croaks.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message