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

Ascending rule match with RelSubset operand doesn't work

    XMLWordPrintableJSON

    Details

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

      Description

      Given a rule with match pattern operand(Filter, operand(RelSubset)), when we add a new RelSubset into the set, planner will fire rules for RelSubset.
      But in VolcanoRuleCall.matchRecurse, if !inputRels.contains(previous), it will skip. Obviously, the input rels will never contain a RelSubset, hence fails to match the rule.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              hyuan Haisheng Yuan
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: