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/18 11:24:41 UTC
[jira] [Commented] (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=15972514#comment-15972514 ]
Jesus Camacho Rodriguez commented on HIVE-15619:
------------------------------------------------
[~nishantbangarwa], HIVE-15708 has gone in, thus I think we can rebase this patch to use the new rules and enable them in Hive.
> 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
> Attachments: HIVE-15619.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)