[
https://issues.apache.org/jira/browse/HADOOP-14918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14918:
------------------------------------
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.-
was:
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.
> remove the Local Dynamo DB test option
> --------------------------------------
>
> Key: HADOOP-14918
> URL: https://issues.apache.org/jira/browse/HADOOP-14918
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.9.0, 3.0.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-14918-001.patch
>
>
> 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.-
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
