You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@calcite.apache.org by "Vladimir Dolzhenko (JIRA)" <ji...@apache.org> on 2017/12/22 12:22:00 UTC

[jira] [Created] (CALCITE-2106) Where IN clause performs in memory filtration with > 20 values

Vladimir Dolzhenko created CALCITE-2106:
-------------------------------------------

             Summary: Where IN clause performs in memory filtration with > 20 values
                 Key: CALCITE-2106
                 URL: https://issues.apache.org/jira/browse/CALCITE-2106
             Project: Calcite
          Issue Type: Bug
            Reporter: Vladimir Dolzhenko
            Assignee: Julian Hyde


Let's say we have a query
{code}
select id, name, somevalue from table where name in (...)
{code}

SqlToRelConverter has the limitation of 20 items for IN-clause - and therefore query plans looks like TableScan with further EnumerableValues (that implies entire table load into the memory).

In case with Mongo (and I think many other cases that contains huge amount of data) it could 
lead to OOM while native (for data source) IN is available . 




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)