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

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

                Author: ASF GitHub Bot
            Created on: 06/Jan/21 14:35
            Start Date: 06/Jan/21 14:35
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on pull request #2551:
URL: https://github.com/apache/hadoop/pull/2551#issuecomment-755334143


   +1; merged to trunk. Not pulled in to -3.3, but only because the asf repo 
seems to be out of sync and so I can't easily do the cherrypick
   
   @bilaharith could you do a test run with this PR applied to branch-3.3? No 
need for a new PR, just do a test run and let us know how it came out


----------------------------------------------------------------
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:
[email protected]


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

    Worklog Id:     (was: 531903)
    Time Spent: 40m  (was: 0.5h)

> ADLFS: Update SDK version from 2.3.6 to 2.3.9
> ---------------------------------------------
>
>                 Key: HADOOP-17444
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17444
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/adl
>    Affects Versions: 3.4.0
>            Reporter: Bilahari T H
>            Assignee: Bilahari T H
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Update SDK version from 2.3.6 to 2.3.9



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to