[HADOOP-14918] Remove the Local Dynamo DB test option

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0, 3.0.0
• Fix Version/s: 3.2.0, 3.1.4, 2.10.1
• Component/s: fs/s3
• Assignee: Gabor Bota
• Reporter: Steve Loughran
• Created: 01/Oct/17 19:03
• Updated: 23/Mar/20 20:57
• Resolved: 23/Mar/20 15:23

Description

I'm going to propose cutting out the localdynamo test option for s3guard

• the local DDB JAR is unmaintained/lags the SDK We work with...eventually there'll be differences in API.
• as the local dynamo DB is unshaded. it complicates classpath setup for the build. Remove it and there's no need to worry about versions of anything other than the shaded AWS
• it complicates test runs. Now we need to test for both localdynamo and real dynamo
• but we can't ignore real dynamo, because that's the one which matters

While the local option promises to reduce test costs, really, it's just adding complexity. If you are testing with s3guard, you need to have a real table to test against., And with the exception of those people testing s3a against non-AWS, consistent endpoints, everyone should be testing with S3Guard.

Straightforward to remove.

Issue Links

• blocks: YARN-8374 Upgrade objenesis to 2.6
• is depended upon by: HADOOP-14734 add option to tag DDB table(s) created
• is related to: HADOOP-14068 Add integration test version of TestMetadataStore for DynamoDB
• is related to: HADOOP-16175 S3Guard to add DynamoDBLocal Support
• is related to: HADOOP-15301 TestDynamoDBMetadataStore test case fails on PPC
• is related to: HADOOP-15636 Add ITestDynamoDBMetadataStore
• relates to: YARN-8338 TimelineService V1.5 doesn't come up after HADOOP-15406
• links to: GitHub Pull Request #1864