Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-3335

Allow single-node optimization with joins.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • Impala 2.5.0
    • Impala 4.0.0
    • Frontend

    Description

      Now that IMPALA-561 has been fixed, we can remove the workaround that disables the our single-node optimization for any plan with joins. See MaxRowsProcessedVisitor.java:

      } else if (caller instanceof HashJoinNode || caller instanceof NestedLoopJoinNode) {
        // Revisit when multiple scan nodes can be executed in a single fragment, IMPALA-561
        abort_ = true;
        return;
      }
      

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            stakiar Sahil Takiar
            alex.behm Alexander Behm
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment