[
https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411562#comment-16411562
]
slim bouguerra commented on HIVE-18780:
---------------------------------------
[~ashutoshc] FYI please do not merge this before I get to rebase the patch with
master + calcite 16 https://issues.apache.org/jira/browse/HIVE-18957
> Improve schema discovery For Druid Storage Handler
> --------------------------------------------------
>
> Key: HIVE-18780
> URL: https://issues.apache.org/jira/browse/HIVE-18780
> Project: Hive
> Issue Type: Improvement
> Components: Druid integration
> Reporter: slim bouguerra
> Assignee: slim bouguerra
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18780.11.patch, HIVE-18780.12.patch,
> HIVE-18780.2.patch, HIVE-18780.4.patch, HIVE-18780.5.patch,
> HIVE-18780.6.patch, HIVE-18780.7.patch, HIVE-18780.8.patch, HIVE-18780.patch,
> HIVE-18780.patch
>
>
> Currently, Druid Storage adapter issues a Segment metadata Query every time
> the query is of type Select or Scan. Not only that but then every input split
> (map) will do the same as well since it is using the same Serde, this is very
> expensive and put a lot of pressure on the Druid Cluster. The way to fix this
> is to add the schema out of the calcite plan instead of serializing the query
> itself as part of the Hive query context.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
