You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Madhuvanthi Radhakrishnan (JIRA)" <ji...@apache.org> on 2017/11/10 23:34:00 UTC

[jira] [Commented] (AMBARI-22355) New endpoint at ServiceLevel for configurations - POST, GET

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

Madhuvanthi Radhakrishnan commented on AMBARI-22355:
----------------------------------------------------

[~swapanshridhar], [~jluniya],
Please review the attached patch. 
Due to addition of a new column service_id in clusterconfig table, it references the id in clusterservices. But there is no unique key constraint defined on the id column in clusterservices. Hence added it. Also, moved clusterconfig CREATE ddl to occur after clusterservices due to the foreign key reference.

> New endpoint at ServiceLevel for configurations - POST, GET
> -----------------------------------------------------------
>
>                 Key: AMBARI-22355
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22355
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Madhuvanthi Radhakrishnan
>            Assignee: Madhuvanthi Radhakrishnan
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-22355_addendum.patch
>
>
> In a multi service instance scenario we could have more than one service instance running in a cluster. 
> Two Zookeepers (ZK1, ZK2) running in a cluster. 
> We need to distinguish between configs for ZK1 and for ZK2 
> To support multi instance scenario, the configurations API endpoint will be moved from cluster-level to service-level
> New API Endpoint
> api/v2/clusters/<cluster-name>/servicegroups/<service-group-name>/services/<service-name>/configurations



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