You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Vladimir Sitnikov (JIRA)" <ji...@apache.org> on 2018/10/11 13:09:00 UTC
[jira] [Commented] (CALCITE-2617) FilterProjectTransposeRule should
allow filter conditions with correlated variables to be pushed down
[ https://issues.apache.org/jira/browse/CALCITE-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646402#comment-16646402 ]
Vladimir Sitnikov commented on CALCITE-2617:
--------------------------------------------
Should it be enabled by default?
Should it be configurable via connection property? (or -D or whatever)
> FilterProjectTransposeRule should allow filter conditions with correlated variables to be pushed down
> -----------------------------------------------------------------------------------------------------
>
> Key: CALCITE-2617
> URL: https://issues.apache.org/jira/browse/CALCITE-2617
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.17.0
> Reporter: Stamatis Zampetakis
> Assignee: Julian Hyde
> Priority: Major
> Fix For: 1.18.0
>
>
> The rule always forbids conditions with correlated variables to be pushed down (as of [CALCITE-769|https://issues.apache.org/jira/browse/CALCITE-769] to avoid certain problems in the decorrelation of the query). However, in the general context of query optimization, it is beneficial to push-down filters and the fact that there is a correlated variable is not a reason to skip this optimization.
> In order to avoid regressions, and at the same time enable correlated conditions to be pushed down we should make the pushing of correlated variables configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)