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

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

                Author: ASF GitHub Bot
            Created on: 12/Jan/22 17:29
            Start Date: 12/Jan/22 17:29
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on pull request #3879:
URL: https://github.com/apache/hadoop/pull/3879#issuecomment-1011285697


   thanks!
   merged in. before i close the JIRA, what is your username there so I can 
give you the credit?


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

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

> remove misleading fs.s3a.delegation.tokens.enabled prompt
> ---------------------------------------------------------
>
>                 Key: HADOOP-16223
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16223
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.3.3
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> There's a reference to the option fs.s3a.delegation.tokens.enabled, but 
> that's not used in the final HADOOP-14556, which runs straight off the 
> fs.s3a.delegation.token.binding value. 
> Remove the entry to avoid confusion



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to