[ https://issues.apache.org/jira/browse/HADOOP-14507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341690#comment-16341690 ]
genericqa commented on HADOOP-14507: ------------------------------------ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s{color} | {color:blue} Docker mode activated. {color} | | {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color} | {color:red} HADOOP-14507 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} | \\ \\ || Subsystem || Report/Notes || | JIRA Issue | HADOOP-14507 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12907942/HADOOP-14507-006.patch | | Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/14040/console | | Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org | This message was automatically generated. > extend per-bucket secret key config with explicit getPassword() on > fs.s3a.$bucket.secret,key > -------------------------------------------------------------------------------------------- > > Key: HADOOP-14507 > URL: https://issues.apache.org/jira/browse/HADOOP-14507 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 2.8.1 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Major > Attachments: HADOOP-14507-001.patch, HADOOP-14507-002.patch, > HADOOP-14507-003.patch, HADOOP-14507-004.patch, HADOOP-14507-005.patch, > HADOOP-14507-006.patch, HADOOP-14507-006.patch > > > Per-bucket jceks support turns out to be complex as you have to manage > multiple jecks files & configure the client to ask for the right one. This is > because we're calling {{Configuration.getPassword{"fs,s3a.secret.key"}}. > If before that, we do a check for the explict id, key, session key in the > properties {{fs.s3a.$bucket.secret}} ( & c), we could have a single JCEKs > file with all the secrets for different bucket. You would only need to > explicitly point the base config to the secrets file, and the right > credentials would be picked up, if set -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org