You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Xi Wang (JIRA)" <ji...@apache.org> on 2014/08/27 00:35:58 UTC
[jira] [Commented] (AMBARI-7026) Config History: FE change to
integrate new name 'service_config_version' in api
[ https://issues.apache.org/jira/browse/AMBARI-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111483#comment-14111483 ]
Xi Wang commented on AMBARI-7026:
---------------------------------
patch part 1 attached.
For now, the api worked for:
http://c6404.ambari.apache.org:8080/api/v1/clusters/cl456/configurations/service_config_versions?service_name=HDFS&serviceconfigversion=5
However, the expected api call should be:
http://c6404.ambari.apache.org:8080/api/v1/clusters/cl456/configurations/service_config_versions?service_name=HDFS&service_config_version=5
Need anther patch when this got fixed.
> Config History: FE change to integrate new name 'service_config_version' in api
> -------------------------------------------------------------------------------
>
> Key: AMBARI-7026
> URL: https://issues.apache.org/jira/browse/AMBARI-7026
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.7.0
> Reporter: Xi Wang
> Assignee: Xi Wang
> Fix For: 1.7.0
>
> Attachments: AMBARI-7026.patch
>
>
> Old name: 'serviceconfigversions' has been changed into 'service_config_versions' when doing api call.
> FE should integrate this change.
--
This message was sent by Atlassian JIRA
(v6.2#6252)