You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2018/11/17 04:20:00 UTC
[jira] [Commented] (CALCITE-2671) GeodeFilter change to transform
multiple OR s to use IN SET OQL predicate to significantly improve query
performance
[ https://issues.apache.org/jira/browse/CALCITE-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690367#comment-16690367 ]
Julian Hyde commented on CALCITE-2671:
--------------------------------------
[~asereda], Looks like you're reviewing this. Can you make sure it gets committed when it's ready?
> GeodeFilter change to transform multiple OR s to use IN SET OQL predicate to significantly improve query performance
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-2671
> URL: https://issues.apache.org/jira/browse/CALCITE-2671
> Project: Calcite
> Issue Type: Improvement
> Components: geode
> Reporter: Sandeep Chada
> Assignee: Julian Hyde
> Priority: Major
>
> In Geode when we are querying thousands of rows using an IN query, IN SET query predicate gives high query performance than multiple OR s.
> I am making the change in the GeodeFilter translateMatch function by first checking if IN SET is applicable then only use it, otherwise the multiple OR code is called.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)