Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15620 Über-jira: S3A phase VI: Hadoop 3.3 features
  3. HADOOP-15955

declare that fs.s3a.ext. is a prefix for arbitrary extensions

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: 3.2.0
    • Fix Version/s: None
    • Component/s: fs/s3
    • Labels:
      None
    • Target Version/s:

      Description

      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

      1. applications/extensions MUST NOT add their own config options under fs.s3a.
      2. anyone is free to use "fs.s3a.ext.$product." options in s3a.
      3. we promise not to go near those options in the S3A module
      4. 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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              stevel@apache.org Steve Loughran
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: