ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21317) Config update API should not need to have a unique tag, BE can auto add the tag when it is missing
Date Mon, 26 Jun 2017 13:59:00 GMT

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

Hadoop QA commented on AMBARI-21317:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12874497/AMBARI-21317.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 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:red}-1 core tests{color}.  The test build failed in [ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/11678//artifact/patch-work/testrun_ambari-server.txt]


Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11678//console

This message is automatically generated.

> Config update API should not need to have a unique tag, BE can auto add the tag when
it is missing
> --------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21317
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21317
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.5.1
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-21317.patch
>
>
> Currently, a config update expects a tag value from the client calling the API. It should
be optional and if not provided then BE should generate a unique tag and auto add.
> {code}
> [{"Clusters":{
>   "desired_config":[{
>     "type":"zoo.cfg",
>     "tag":"version1495042583018",
>     "properties":{...
> ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message