[
https://issues.apache.org/jira/browse/CALCITE-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881689#comment-15881689
]
slim bouguerra commented on CALCITE-1655:
-----------------------------------------
[~julianhyde] i agree that we should keep the OR but i think that re-writing
IN to bunch of OR is not necessary. In fact i bet all the DB stores perform
better with IN than multiple OR clauses.
As you can see here https://issues.apache.org/jira/browse/HIVE-16025 the
re-writing is not happening because HIVE likes to keep IN rather than
evaluating all the ORs individually.
> Add In filter to druid adapter.
> -------------------------------
>
> Key: CALCITE-1655
> URL: https://issues.apache.org/jira/browse/CALCITE-1655
> Project: Calcite
> Issue Type: Bug
> Components: druid
> Reporter: slim bouguerra
> Assignee: Julian Hyde
>
> The druid calcite adapter throw an exception when an IN filter is used.
> This happens only in hive because in calcite project the IN filter is
> transformed to OR automatically.
> Since this rule does not kick in HIVE and it is better to use the native IN
> filter from druid instead having huge number of OR clauses i will send a
> patch that adds the IN filter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
