You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "zhen wang (JIRA)" <ji...@apache.org> on 2018/03/07 02:47:00 UTC
[jira] [Issue Comment Deleted] (CALCITE-2106) Where IN clause
performs in memory filtration with > 20 values
[ https://issues.apache.org/jira/browse/CALCITE-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhen wang updated CALCITE-2106:
-------------------------------
Comment: was deleted
(was: [~vladimir.dolzhenko] what's your expected behavior here? more friendly/specific error message ?)
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)