Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-36822

BroadcastNestedLoopJoinExec should use all condition instead of non-equi condition

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.2.0
    • 3.3.0
    • SQL
    • None

    Description

      At JoinSelection, with ExtractEquiJoinKeys, we use `nonEquiCond` as the join condition. It's wrong since there should exist some equi condition.

      Seq(joins.BroadcastNestedLoopJoinExec(
        planLater(left), planLater(right), buildSide, joinType, nonEquiCond))
      

      But it's should not be a bug, since we always use the smj as the default join strategy for ExtractEquiJoinKeys.

      Attachments

        Activity

          People

            ulysses XiDuo You
            ulysses XiDuo You
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: