[
https://issues.apache.org/jira/browse/HADOOP-16409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880601#comment-16880601
]
Hudson commented on HADOOP-16409:
---------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16869 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16869/])
HADOOP-16409. Allow authoritative mode on non-qualified paths. (gabor.bota: rev
de6b7bc67ace7744adb0320ee7de79cf28259d2d)
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/DynamoDBMetadataStore.java
* (edit)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestAuthoritativePath.java
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/S3Guard.java
> Allow authoritative mode on non-qualified paths
> -----------------------------------------------
>
> Key: HADOOP-16409
> URL: https://issues.apache.org/jira/browse/HADOOP-16409
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Major
> Fix For: 3.3.0
>
>
> fs.s3a.authoritative.path currently requires a qualified URI (e.g.
> s3a://bucket/path) which is how I see this being used most immediately, but
> it also make sense for someone to just be able to configure /path, if all of
> their buckets follow that pattern, or if they're providing configuration
> already in a bucket-specific context (e.g. job-level configs, etc.) Just need
> to qualify whatever is passed in to allowAuthoritative to make that work.
> Also, in HADOOP-16396 Gabor pointed out a few whitepace nits that I neglected
> to fix before merging.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
