You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2017/06/22 11:27:00 UTC
[jira] [Updated] (AMBARI-21317) Config update API should not need
to have a unique tag, BE can auto add the tag when it is missing
[ https://issues.apache.org/jira/browse/AMBARI-21317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitaly Brodetskyi updated AMBARI-21317:
---------------------------------------
Status: Patch Available (was: Open)
> 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: Bug
> 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)