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

Hadoop QA commented on HADOOP-13899:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} 
| {color:red} HADOOP-13899 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-13899 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12843017/HADOOP-13455-HADOOP-13899-003.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/11264/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> tune dynamodb client & tests
> ----------------------------
>
>                 Key: HADOOP-13899
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13899
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-13455-HADOOP-13899-003.patch, 
> HADOOP-13899-HADOOP-13345-001.patch, HADOOP-13899-HADOOP-13345-002.patch
>
>
> While setting up clients for testing dynamo DB, make the tweaks to the dynamo 
> store and the s3guard code for better use downstream. These are the kind of 
> things we need to round off the code for production use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to