[jira] [Resolved] (HADOOP-16343) Add option for a prefix to put in front of every s3guard table

["Steve Loughran (Jira)" <ji...@apache.org>]

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

Steve Loughran resolved HADOOP-16343.
-------------------------------------
    Resolution: Won't Fix

> Add option for a prefix to put in front of every s3guard table
> --------------------------------------------------------------
>
>                 Key: HADOOP-16343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16343
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.2.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> 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|https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html] put a limit of 255 chars; table prefix should short, e.g. "s3a."



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org