Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-17861 Store data source partitions in metastore and push partition pruning into metastore
  3. SPARK-18507

Major performance regression in SHOW PARTITIONS on partitioned Hive tables

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete CommentsDelete
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 2.1.0
    • 2.1.0
    • SQL
    • None

    Description

      Commit ccb11543048dccd4cc590a8db1df1d9d5847d112 (https://github.com/apache/spark/commit/ccb11543048dccd4cc590a8db1df1d9d5847d112) appears to have introduced a major regression in the performance of the Hive SHOW PARTITIONS command. Running that command on a Hive table with 17,337 partitions in the spark-sql shell with the parent commit of ccb1154 takes approximately 7.3 seconds. Running the same command with commit ccb1154 takes approximately 250 seconds.

      I have not had the opportunity to complete a thorough investigation, but I suspect the problem lies in the diff hunk beginning at https://github.com/apache/spark/commit/ccb11543048dccd4cc590a8db1df1d9d5847d112#diff-159191585e10542f013cb3a714f26075L675. If that's the case, this performance issue should manifest itself in other areas as this programming pattern was used elsewhere in this commit.

      Attachments

        Issue Links

        Activity

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

          People

            cloud_fan Wenchen Fan Assign to me
            michael Michael MacFadden
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment