Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-16829 Über-jira: S3A Hadoop 3.4 features
  3. HADOOP-16343

Add option for a prefix to put in front of every s3guard table

    XMLWordPrintableJSON

    Details

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

      Description

      with DDB on demand, there's no cost in $ to having a table per bucket, and some security isolation benefits. But if you tell applications they can create DDB tables for every s3 bucket they encounter, their names may clash with other DDB tables, and it becomes hard to identify which tables in a region are s3.

      Proposed: add a fs.s3a.s3guard.table.prefix option which lets you define the prefix to put in front of any inferred table name, so providing the isolation

      note, AWS DDB naming rules put a limit of 255 chars; table prefix should short, e.g. "s3a."

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated: