[
https://issues.apache.org/jira/browse/HIVE-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesus Camacho Rodriguez updated HIVE-14466:
-------------------------------------------
Description:
Leverage the existing code in Calcite (CALCITE-1121) to push operators into
DruidQuery. Currently Project, Filter, and Aggregate operators can be pushed,
and Druid *Select* and *GroupBy* queries are recognized. However, other query
types such as *Timeseries* and *TopN*, which are known to be Druid greater
assets, are not recognized as such.
Hence, we should extend the Calcite based code to push operators into
DruidQuery (Scan) that can lead to the recognition of these query types.
Further, we need to extend the logic to transform a DruidQuery containing a
complex plan into a JSON query formatted for Druid.
was:
Leverage the existing code in Calcite (CALCITE-1121) to push operators into
DruidQuery. Currently Project, Filter, and Aggregate operators can be pushed,
and Druid Select and GroupBy queries are recognized. However, other query types
such as Timeseries and TopN, which are known to be Druid greater assets, are
not recognized as such.
Hence, we should extend the Calcite based code to push operators into
DruidQuery (Scan) that can lead to the recognition of these query types.
Further, we need to extend the logic to transform a DruidQuery containing a
complex plan into a JSON query formatted for Druid.
> Extend Calcite capabilities to transform plan into Druid query
> --------------------------------------------------------------
>
> Key: HIVE-14466
> URL: https://issues.apache.org/jira/browse/HIVE-14466
> Project: Hive
> Issue Type: Sub-task
> Components: Druid integration
> Affects Versions: 2.2.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
>
> Leverage the existing code in Calcite (CALCITE-1121) to push operators into
> DruidQuery. Currently Project, Filter, and Aggregate operators can be pushed,
> and Druid *Select* and *GroupBy* queries are recognized. However, other query
> types such as *Timeseries* and *TopN*, which are known to be Druid greater
> assets, are not recognized as such.
> Hence, we should extend the Calcite based code to push operators into
> DruidQuery (Scan) that can lead to the recognition of these query types.
> Further, we need to extend the logic to transform a DruidQuery containing a
> complex plan into a JSON query formatted for Druid.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
