[
https://issues.apache.org/jira/browse/HADOOP-14734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612840#comment-16612840
]
Aaron Fabbri commented on HADOOP-14734:
---------------------------------------
I tested this in us-west-2 by:
* Running all integration and unit tests with -Ds3guard -Ddynamo
* Doing the same with {{fs.s3a.s3guard.ddb.table.create}} and
{{fs.s3a.s3guard.ddb.table.tag.blah}} set and confirming it creates a tagged
table.
* Using the CLI to manually create a tagged dynamo table.
Will commit shortly.
One possible future issue with the tagging integration test: We've seen that
dynamo table metadata seems to be eventually consistent (i.e. table names are
cached and create/destroy table is not always immediately visible). I didn't
see any flakiness but if the part of the test that reads back the tags you set
ever becomes flaky we may need to put a retry around it. Not sure this is
needed at this point, but FYI.
> add option to tag DDB table(s) created
> --------------------------------------
>
> Key: HADOOP-14734
> URL: https://issues.apache.org/jira/browse/HADOOP-14734
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0-beta1
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Minor
> Attachments: HADOOP-14734-001.patch, HADOOP-14734-002.patch,
> HADOOP-14734-003.patch, HADOOP-14734.004.patch, HADOOP-14734.005.patch
>
>
> Many organisations have a "no untagged" resource policy; s3guard runs into
> this when a table is created untagged. If there's a strict "delete untagged
> resources" policy, the tables will go without warning.
> Proposed: we add an option which can be used to declare the tags for a table
> when created, use it in creation. No need to worry about updating/viewing
> tags, as the AWS console can do that
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
