Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-7292 Hive on Spark
  3. HIVE-9574

Lazy computing in HiveBaseFunctionResultList may hurt performance [Spark Branch]

Log workAgile BoardRank to TopRank to BottomVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.1.0
    • Spark
    • None

    Description

      RowContainer.first may call InputFormat.getSplits, which is expensive. If we switch container and backupContainer frequently in HiveKVResultCache, it will downgrade performance.

      Attachments

        1. HIVE-9574.1-spark.patch
          30 kB
          Jimmy Xiang
        2. HIVE-9574.2-spark.patch
          29 kB
          Jimmy Xiang
        3. HIVE-9574.3-spark.patch
          29 kB
          Jimmy Xiang
        4. HIVE-9574.4-spark.patch
          29 kB
          Jimmy Xiang
        5. HIVE-9574.5-spark.patch
          23 kB
          Jimmy Xiang
        6. HIVE-9574.6-spark.patch
          23 kB
          Jimmy Xiang

        Activity

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

          People

            jxiang Jimmy Xiang Assign to me
            lirui Rui Li
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment