Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-17276

Check max shuffle size when converting to dynamically partitioned hash join

Log workAgile BoardRank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.0.0
    • 3.0.0
    • Physical Optimizer

    Description

      Currently we only check that the max number of entries in the hashmap for a MapJoin surpasses a certain threshold to decide whether to execute a dynamically partitioned hash join.

      We would like to factor the size of the large input that we will shuffle for the dynamically partitioned hash join into the cost model too.

      Attachments

        1. HIVE-17276.01.patch
          14 kB
          Jesus Camacho Rodriguez
        2. HIVE-17276.02.patch
          15 kB
          Jesus Camacho Rodriguez
        3. HIVE-17276.03.patch
          15 kB
          Jesus Camacho Rodriguez
        4. HIVE-17276.patch
          14 kB
          Jesus Camacho Rodriguez

        Issue Links

        Activity

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

          People

            jcamachorodriguez Jesus Camacho Rodriguez Assign to me
            jcamachorodriguez Jesus Camacho Rodriguez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment