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

Set the default threshold for fetch task conversion to 1Gb

Log workAgile BoardRank to TopRank to BottomVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.13.1, 0.14.0
    • 0.14.0
    • None
    • Set the simple fetch task conversion to "more" with a default threshold of 1Gb

    Description

      Currently, modifying the value of hive.fetch.task.conversion to "more" results in a dangerous setting where small scale queries function, but large scale queries crash.

      This occurs because the default threshold of -1 means apply this optimization for a petabyte table.

      I am testing a variety of queries with the setting "more" (to make it the default option as suggested by HIVE-887) change the default threshold for this feature to a reasonable 1Gb.

      Attachments

        1. HIVE-7397.1.patch
          1 kB
          Gopal Vijayaraghavan
        2. HIVE-7397.2.patch
          5 kB
          Gopal Vijayaraghavan
        3. HIVE-7397.3.patch
          5 kB
          Gopal Vijayaraghavan
        4. HIVE-7397.4.patch.txt
          18 kB
          Navis Ryu
        5. HIVE-7397.5.patch
          18 kB
          Gopal Vijayaraghavan
        6. HIVE-7397.6.patch.txt
          28 kB
          Navis Ryu

        Activity

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

          People

            gopalv Gopal Vijayaraghavan Assign to me
            gopalv Gopal Vijayaraghavan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment