[
https://issues.apache.org/jira/browse/HADOOP-14734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364643#comment-16364643
]
Abraham Fine commented on HADOOP-14734:
---------------------------------------
Looking at the remaining findbugs warning from:
[https://builds.apache.org/job/PreCommit-HADOOP-Build/14112/artifact/out/diff-checkstyle-hadoop-tools_hadoop-aws.txt]
{quote}./hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/DynamoDBMetadataStore.java:251:
private DynamoDB createDynamoDB(Configuration conf, String s3Region):49:
'conf' hides a field. [HiddenField]
{quote}
This is strange to me since this does not appear to have changed between my
patch and trunk so I'm not sure why it was not present before.
> 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, HADOOP-14734-002.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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
