[
https://issues.apache.org/jira/browse/IMPALA-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Carlin updated IMPALA-13439:
----------------------------------
Description:
Comment from code review for
https://gerrit.cloudera.org/#/c/21911/3//COMMIT_MSG@13
For large IN-lists, Calcite supports the LogicalValues relnode (derived from
Values) and converts it to a join [see comments in [1]). This would be the most
efficient representation but we would need a physical representation of this as
well, so something to consider for future work.
was:
Comment from code review for [https://gerrit.cloudera.org/#/c/21911/]
For large IN-lists, Calcite supports the LogicalValues relnode (derived from
Values) and converts it to a join [see comments in [1]). This would be the most
efficient representation but we would need a physical representation of this as
well, so something to consider for future work.
> Make IN clause more efficient in Calcite Planner
> ------------------------------------------------
>
> Key: IMPALA-13439
> URL: https://issues.apache.org/jira/browse/IMPALA-13439
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Steve Carlin
> Assignee: Steve Carlin
> Priority: Major
>
> Comment from code review for
> https://gerrit.cloudera.org/#/c/21911/3//COMMIT_MSG@13
> For large IN-lists, Calcite supports the LogicalValues relnode (derived from
> Values) and converts it to a join [see comments in [1]). This would be the
> most efficient representation but we would need a physical representation of
> this as well, so something to consider for future work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
