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

AvroSerde performance problem caused by HIVE-3833

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

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.11.0
    • None
    • Query Processor
    • None

    Description

      HIVE-3833 fixed the targeted problem and made Hive to use partition-level metadata to initialize object inspector. In doing that, however, it goes thru every file under the table to access the partition metadata, which is very inefficient, especially in case of multiple files per partition. This causes more problem for AvroSerde because AvroSerde initialization accesses schema, which is located on file system. As a result, before hive can process any data, it needs to access every file for a table, which can take long enough to cause job failure because of lack of job progress.

      The improvement can be made so that partition metadata is only access once per partition.

      Attachments

        1. HIVE-5298.patch
          3 kB
          Xuefu Zhang
        2. HIVE-5298.1.patch
          3 kB
          Xuefu Zhang

        Activity

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

          People

            xuefuz Xuefu Zhang Assign to me
            xuefuz Xuefu Zhang

            Dates

              Created:
              Updated:

              Slack

                Issue deployment