[
https://issues.apache.org/jira/browse/AMBARI-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880179#comment-13880179
]
Siddharth Wagle commented on AMBARI-4334:
-----------------------------------------
+1 patch looks good.
> Add Request Schedule as an object to the Request with properties
> ----------------------------------------------------------------
>
> Key: AMBARI-4334
> URL: https://issues.apache.org/jira/browse/AMBARI-4334
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Fix For: 1.5.0
>
>
> With the new relationship from Request to Request Schedule, the relation ship
> is displayed as an attribute of request.
> This should instead be a map with key as object name "RequestSchedule" and
> the properties of id and href.
> Look at Config Groups example.
> This is to align with the rest of the API and demarcate the relationship
> object even though it is not a subresource.
> Something like:
> {code}
> {
> href: "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/24";,
> Requests: {
> ....,
> request_schedule : {
> href:
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/request_schedules/29";,
> schedule_id: 29,
> },
> .....
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
