[
https://issues.apache.org/jira/browse/AMBARI-23629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-23629.
----------------------------------
Resolution: Fixed
> Review calls GET, PUT, DELETE for Host components and make sure that we call
> them with ID as endpoint instead of name.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-23629
> URL: https://issues.apache.org/jira/browse/AMBARI-23629
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Reporter: Ishan Bhatt
> Assignee: Ishan Bhatt
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Given that Host Component APIs are Id based now to support multi-component
> instances [https://github.com/apache/ambari/pull/477/files], UI need to
> update the calls so that whenever Host Component API calls (GET, PUT, DELETE
> etc) are made, they should refer HOST COMPONENTS via their ID, wherever
> applicable.
> Example:
> The below calls breaks for component ZOOKEEPER_SERVER, when we do a PUT.
> - PUT
> http://<AmbariServer>:8080/api/v1/clusters/c1/hosts/<host_name>/host_components/ZOOKEEPER_SERVER?
> - Body :
> {code:java}
> {"RequestInfo":{"context":"Start ZooKeeper
> Server","operation_level":{"level":"HOST_COMPONENT","cluster_name":"c1","host_name":<host_name>,"service_name":"ZOOKEEPER"}},"Body":{"HostRoles":{"state":"STARTED"}}}
> {code}
> Thus, we need to visit all Host Component API calls from UI perspective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
