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 "Gabor Bota (JIRA)" <ji...@apache.org> on 2019/07/08 17:29:00 UTC

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

     [ https://issues.apache.org/jira/browse/HADOOP-16409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabor Bota resolved HADOOP-16409.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.3.0

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