Abraham Fine commented on HADOOP-14734:

A couple things to note about the patch:
 * The document based Dynamo API does not appear to expose access to the 
tagging API so we need to keep track of theĀ {{AmazonDynamoDB}} object now. 
 * Each tag needs to be its own property in the config xml since commas are 
allowed in the keys and values of a tag
 * Tags are only added to a table when it is created and there is no retry logic
 * The test must connect to "real DynamoDB" instead of the in-memory version we 
use for some other tests, so it has its own class (since the in-memory version 
does not appear to support tagging)
 * The test assumes table creation privileges and that 
{{S3GUARD_DDB_REGION_KEY}} is being provided

> 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: Abraham Fine
>            Priority: Minor
>         Attachments: HADOOP-14734-001.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

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

Reply via email to