Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-2275

Do not push down NOT condition in JOIN

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.16.0
    • Fix Version/s: 1.17.0
    • Component/s: core
    • Labels:
      None

      Description

      Using logical NOT operator in Join condition leads to mistakenly push down this condition. Then LogicalProject is created with RexCall expression. It prevents for further inferring predicates (by using JoinPushTransitivePredicatesRule, for instance).

      Query example:

      select * from sales.emp d join sales.emp e on e.deptno = d.deptno and d.deptno not in (4, 6)
      

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              vitalii Vitalii Diravka
              Reporter:
              vitalii Vitalii Diravka

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment