You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2019/07/03 20:29:00 UTC

[jira] [Created] (HADOOP-16409) Allow authoritative mode on non-qualified paths

Sean Mackrory created HADOOP-16409:
--------------------------------------

             Summary: 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
            Reporter: Sean Mackrory
            Assignee: Sean Mackrory


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: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org