[ 
https://issues.apache.org/jira/browse/HADOOP-17594?focusedWorklogId=568313&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-568313
 ]

ASF GitHub Bot logged work on HADOOP-17594:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Mar/21 12:44
            Start Date: 18/Mar/21 12:44
    Worklog Time Spent: 10m 
      Work Description: ayushtkn commented on pull request #2786:
URL: https://github.com/apache/hadoop/pull/2786#issuecomment-801894903


   Ran the S3A Test:
   ```
   [INFO] -------------------------------------------------------
   [INFO]  T E S T S
   [INFO] -------------------------------------------------------
   [INFO] Running org.apache.hadoop.fs.contract.s3a.ITestS3AContractDistCp
   [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
182.667 s - in org.apache.hadoop.fs.contract.s3a.ITestS3AContractDistCp
   [INFO] 
   [INFO] Results:
   [INFO] 
   [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
   ```
   
   `
   AWS_REGION=ap-south-1
   `


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 568313)
    Time Spent: 20m  (was: 10m)

> DistCp: Expose the JobId for applications executing through run method
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-17594
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17594
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Ayush Saxena
>            Assignee: Ayush Saxena
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Presently the job id is set in the JobConf, and If an application submits 
> using execute method, it can fetch the job id, but if it goes through the run 
> method flow, There isn't a way to get the job id.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to