[
https://issues.apache.org/jira/browse/AMBARI-15870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240479#comment-15240479
]
Hadoop QA commented on AMBARI-15870:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12798586/rb46169.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.RequestResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6432//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6432//console
This message is automatically generated.
> Add dryrun method on request object.
> ------------------------------------
>
> Key: AMBARI-15870
> URL: https://issues.apache.org/jira/browse/AMBARI-15870
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Ajit Kumar
> Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb46169.patch
>
>
> To implement dry-run version of an API, request needs to be parsed manually
> to figure out if request has dry-run directive.
> It will be good to add a method on Request object method itself which
> centralizes parsing and logic for figuring out dry-run directive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
