[
https://issues.apache.org/jira/browse/HADOOP-16252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818010#comment-16818010
]
Ben Roling commented on HADOOP-16252:
-------------------------------------
bq. Are the tests still actually creating tables, as I think we might want to
turn that option off, at least until the creation of on-demand tables is
supported. I fear test run failures running up bills if the test suite is
interrupted
Yes, the tests are definitely creating tables and could leave tables around
that run up bills if they abort uncleanly. The change to use on-demand tables
will definitely help avoid that.
> Use configurable dynamo table name prefix in S3Guard tests
> ----------------------------------------------------------
>
> Key: HADOOP-16252
> URL: https://issues.apache.org/jira/browse/HADOOP-16252
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Reporter: Ben Roling
> Priority: Major
>
> Table names are hardcoded into tests for S3Guard with DynamoDB. This makes
> it awkward to set up a least-privilege type AWS IAM user or role that can
> successfully execute the full test suite. You either have to know all the
> specific hardcoded table names and give the user Dynamo read/write access to
> those by name or just give blanket read/write access to all Dynamo tables in
> the account.
> I propose the tests use a configuration property to specify a prefix for the
> table names used. Then the full test suite can be run by a user that is
> given read/write access to all tables with names starting with the configured
> prefix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
