[jira] [Resolved] (HIVE-14465) Recognize scan of Druid table in Calcite optimizer

["Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-14465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesus Camacho Rodriguez resolved HIVE-14465.
--------------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0

Pushed with HIVE-14217.

> Recognize scan of Druid table in Calcite optimizer
> --------------------------------------------------
>
>                 Key: HIVE-14465
>                 URL: https://issues.apache.org/jira/browse/HIVE-14465
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Druid integration
>    Affects Versions: 2.2.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>             Fix For: 2.2.0
>
>
> If a table is handled by DruidStorageHandler, we should be able to recognize it in Calcite. This way we will be able to apply rules in the optimizer to push an operator pipeline into the DruidScan. This will help us generating Druid featured queries e.g. timeseries, topn, groupby, or select.
> For that purpose, we need to introduce a DruidQuery operator based on TableScan. In particular, we should leverage the code introduced in CALCITE-1121. Other operators will be pushed to DruidQuery if they can be executed by Druid i.e. the decision will be made statically (if we can push computation to Druid, we will do it). However, in the future the decision should be cost-based.



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