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

Improve progress-reporting in TezProcessor

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
    • 2.2.0, 2.4.0, 3.0.0
    • 2.2.1, 2.4.0, 3.0.0
    • None
    • None

    Description

      Another one on behalf of Selina Zhang and Chris Drome. Following the example in Apache Tez's MapProcessor, TezProcessor ought to use ProgressHelper to report progress for a Tez task. As per Kuhu Shukla's advice,

      Tez... provides getProgress() API for AbstractLogicalInput(s) which will give the correct progress value for a given Input. The TezProcessor(s) in Hive should use this to do something similar to what MapProcessor in Tez does today, which is use/override ProgressHelper to get the input progress and then set the progress on the processorContext.
      ...
      The default behavior of the ProgressHelper class sets the processor progress to be the average of progress values from all inputs.

      This code is whacked from inspired by MapProcessor's use of ProgressHelper.

      (For my reference, YHIVE-978.)

      Attachments

        1. HIVE-17576.2-branch-2.patch
          4 kB
          Mithun Radhakrishnan
        2. HIVE-17576.2.patch
          4 kB
          Mithun Radhakrishnan
        3. HIVE-17576.1.patch
          2 kB
          Mithun Radhakrishnan

        Activity

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

          People

            mithun Mithun Radhakrishnan Assign to me
            mithun Mithun Radhakrishnan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment