[
https://issues.apache.org/jira/browse/HADOOP-15955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703572#comment-16703572
]
Larry McCay commented on HADOOP-15955:
--------------------------------------
This makes sense, especially given the extensibility built into these storage
connectors for find credentials, etc.
+1
> declare that fs.s3a.ext. is a prefix for arbitrary extensions
> -------------------------------------------------------------
>
> Key: HADOOP-15955
> URL: https://issues.apache.org/jira/browse/HADOOP-15955
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Priority: Trivial
>
> it turns out to be useful to use per-bucket config extensions for things like
> delegation tokens.
> To avoid third-party extensions to pollute the fs.s3a. namespace with their
> own config options (So meaning its inevitable things break when we add some
> new fs option), I propose the following policy
> # applications/extensions MUST NOT add their own config options under fs.s3a.
> # anyone is free to use "fs.s3a.ext.$product." options in s3a.
> # we promise not to go near those options in the S3A module
> # it is left to people who add their own settings here to avoid clashing with
> others, This is why you should use a unique product name
> With this specified (where?) then if someone uses some fs.s3a. option which
> gets broken by an updated s3a connector, well, we say "wontfix", —and indeed,
> get to tell them off for doing this.
> Propose: similar for the other stores
--
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
