[
https://issues.apache.org/jira/browse/CALCITE-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749259#comment-17749259
]
Alessandro Solimando edited comment on CALCITE-5872 at 7/31/23 4:22 PM:
------------------------------------------------------------------------
The query does not look like a minimal reproducer, reducing it further will
help you debug it more easily, or alternatively it will make it easier
(therefore more probable) that someone else will pick it up and fix it.
With the input provided so far, we can't really see what is the problem, or
even confirm that there is one, just to check that it would require someone to
set things up, which consumes time.
Therefore, I also suggest to provide (possibly in the ticket description rather
than as a reply comment) at least the original plan (what's translated from SQL
directly, more or less), an intermediate plan which still looks OK, and one
plan which is not OK (ideally the first one which looks bad to you).
For an easy way to activate extra debug logs during query planning you can
refer to this talk
[https://calcite.apache.org/community/#debugging-planning-issues-using-calcites-built-in-loggers]
EDIT: almost forgot, please set also which version of Calcite is affected by
this bug by using the "Affects Version/s" Jira field.
was (Author: asolimando):
The query does not look like a minimal reproducer, reducing it further will
help you debug it more easily, or alternatively it will make it easier
(therefore more probable) that someone else will pick it up and fix it.
With the input provided so far, we can't really see what is the problem, or
even confirm that there is one, just to check that it would require someone to
set things up, which consumes time.
Therefore, I also suggest to provide (possibly in the ticket description rather
than as a reply comment) at least the original plan (what's translated from SQL
directly, more or less), an intermediate plan which still looks OK, and one
plan which is not OK (ideally the first one which looks bad to you).
For an easy way to activate extra debug logs during query planning you can
refer to this talk
[https://calcite.apache.org/community/#debugging-planning-issues-using-calcites-built-in-loggers]
> JoinPushTransitivePredicatesRule will repeatedly insert the condition "is not
> null"
> -----------------------------------------------------------------------------------
>
> Key: CALCITE-5872
> URL: https://issues.apache.org/jira/browse/CALCITE-5872
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: grandfisher
> Priority: Major
>
> JoinPushTransitivePredicatesRule will repeatedly insert the condition "is not
> null" and will always optimize by `VolcanoPlanner`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
