You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/12/05 15:03:00 UTC

[jira] [Commented] (HADOOP-14918) remove the Local Dynamo DB test option

    [ https://issues.apache.org/jira/browse/HADOOP-14918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278679#comment-16278679 ] 

Steve Loughran commented on HADOOP-14918:
-----------------------------------------

I need to pull this for a different reason. The DDB SDK pulls in JDK 1.11.86 and I'm seeing some test run failures (branch-2+ HADOOP-13786) where changes in the AWS exception class hierarchy between the two versions breaks things. 
{code}
testRetryBadRequestIdempotent(org.apache.hadoop.fs.s3a.TestInvoker)  Time elapsed: 0.009 sec  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.fs.s3a.AWSClientIOException.<init>(Ljava/lang/String;Lcom/amazonaws/AmazonClientException;)V
	at org.apache.hadoop.fs.s3a.AWSServiceIOException.<init>(AWSServiceIOException.java:41)
	at org.apache.hadoop.fs.s3a.AWSBadRequestException.<init>(AWSBadRequestException.java:40)
	at org.apache.hadoop.fs.s3a.S3AUtils.translateException(S3AUtils.java:204)
	at org.apache.hadoop.fs.s3a.Invoker.once(Invoker.java:110)
	at org.apache.hadoop.fs.s3a.Invoker.lambda$retry$3(Invoker.java:259)
	at org.apache.hadoop.fs.s3a.Invoker.retryUntranslated(Invoker.java:313)
	at org.apache.hadoop.fs.s3a.Invoker.retry(Invoker.java:255)
	at org.apache.hadoop.fs.s3a.Invoker.retry(Invoker.java:187)
	at org.apache.hadoop.fs.s3a.Invoker.retry(Invoker.java:209)
	at org.apache.hadoop.fs.s3a.TestInvoker.testRetryBadRequestIdempotent(TestInvoker.java:290)
{code}

> 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: 3.0.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org