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

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

                Author: ASF GitHub Bot
            Created on: 20/Sep/21 13:24
            Start Date: 20/Sep/21 13:24
    Worklog Time Spent: 10m 
      Work Description: mehakmeet edited a comment on pull request #3462:
URL: https://github.com/apache/hadoop/pull/3462#issuecomment-922922797


   One commit in a test might be required which is in non-CSE mode, which I am 
currently running. Apart from that main change is in `S3AUtils.java` where we 
are looking up the old values first then using them as default values for the 
new lookup.


-- 
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: 652957)
    Time Spent: 0.5h  (was: 20m)

> Lookup old S3 encryption configs for JCEKS
> ------------------------------------------
>
>                 Key: HADOOP-17922
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17922
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 3.4.0
>            Reporter: Mehakmeet Singh
>            Assignee: Mehakmeet Singh
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> HADOOP-17871 introduces new set of S3 encryption configs which are replaced 
> by old property names during look-up. We need to look-up for both the 
> properties since either could be set in a JCEKS file.



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