hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-9416) Get rid of Extract Operator
Date Fri, 30 Jan 2015 19:49:35 GMT

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

Ashutosh Chauhan commented on HIVE-9416:
----------------------------------------

Plan changes in bucketsortoptimize_insert_4.q looks correct. I have provided explanation on
RB. I think this patch is ready for review. [~navis] Can you take another look? 

> Get rid of Extract Operator
> ---------------------------
>
>                 Key: HIVE-9416
>                 URL: https://issues.apache.org/jira/browse/HIVE-9416
>             Project: Hive
>          Issue Type: Task
>          Components: Query Processor
>            Reporter: Ashutosh Chauhan
>            Assignee: Ashutosh Chauhan
>         Attachments: HIVE-9416.1.patch, HIVE-9416.2.patch, HIVE-9416.3.patch, HIVE-9416.4.patch,
HIVE-9416.5.patch, HIVE-9416.6.patch, HIVE-9416.7.patch, HIVE-9416.patch
>
>
> {{Extract Operator}} has been there for legacy reasons. But there is no functionality
it provides which cant be provided by {{Select Operator}} Instead of having two operators,
one being subset of another we should just get rid of {{Extract}} and simplify our codebase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message