You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2017/04/21 13:48:04 UTC

[jira] [Comment Edited] (HIVE-15619) Column pruner should handle DruidQuery

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

Jesus Camacho Rodriguez edited comment on HIVE-15619 at 4/21/17 1:47 PM:
-------------------------------------------------------------------------

Pushed to master, thanks [~nishantbangarwa]!


was (Author: jcamachorodriguez):
Pushed to master.

> Column pruner should handle DruidQuery
> --------------------------------------
>
>                 Key: HIVE-15619
>                 URL: https://issues.apache.org/jira/browse/HIVE-15619
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Druid integration
>    Affects Versions: 2.2.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Nishant Bangarwa
>             Fix For: 3.0.0
>
>         Attachments: HIVE-15619.01.patch, HIVE-15619.02.patch, HIVE-15619.03.patch
>
>
> Even when we cannot push any operator into Druid, we might be able to prune some of the columns that are read from the Druid sources.
> One solution would be to extend the ColumnPruner so it can push the needed columns into DruidQuery.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)