hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sichi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-2231) Column aliases
Date Tue, 21 Jun 2011 18:35:48 GMT

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

John Sichi commented on HIVE-2231:
----------------------------------

Since views are already a standard way of addressing this, wouldn't it be better to put effort
into fixing any limitations there?


> Column aliases
> --------------
>
>                 Key: HIVE-2231
>                 URL: https://issues.apache.org/jira/browse/HIVE-2231
>             Project: Hive
>          Issue Type: Wish
>          Components: Query Processor
>            Reporter: Adam Kramer
>            Priority: Trivial
>
> It would be nice in several cases to be able to alias column names.
> Say someone in your company CREATEd a TABLE called important_but_named_poorly (alvin
BIGINT, theodore BIGINT, simon STRING) PARTITIONED BY (dave STRING), that indexes the relationship
between an actor (alvin), a target (theodore), and the interaction between them (simon), partitioned
based on the date string (dave). Renaming the columns would break a million pipelines that
are important but ownerless.
> It would be awesome to define an aliasing system as such:
> ALTER TABLE important_but_named_poorly REPLACE COLUMNS (actor BIGINT AKA alvin, target
BIGINT AKA theodore, ixn STRING AKA simon) PARTITIONED BY (ds STRING AKA dave);
> ...which would mean that any user could, e.g., use the term "dave" to refer to ds if
they really wanted to.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message