helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HELIX-396) Make REST api for /instances parseable
Date Wed, 05 Mar 2014 02:53:43 GMT

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

Hudson commented on HELIX-396:
------------------------------

UNSTABLE: Integrated in helix #1236 (See [https://builds.apache.org/job/helix/1236/])
[HELIX-396] Make REST api for /instances parseable (kanak: rev 3399aadb901ac733f27b9aa4658280273095a21e)
* helix-admin-webapp/src/test/java/org/apache/helix/webapp/TestClusterManagementWebapp.java
* helix-admin-webapp/src/main/java/org/apache/helix/webapp/resources/InstancesResource.java


> Make REST api for /instances parseable
> --------------------------------------
>
>                 Key: HELIX-396
>                 URL: https://issues.apache.org/jira/browse/HELIX-396
>             Project: Apache Helix
>          Issue Type: Improvement
>            Reporter: Kanak Biscuitwala
>            Assignee: Kanak Biscuitwala
>
> The current representation for /clusters/clusterName/instances is not parseable since
it is a concatenation of two things that are parseable, i.e.
> [{instanceConfig1}, {instanceConfig2}]{"tag1": ["localhost_1"]}
> What we want instead is everything encapsulated in a single JSON object:
> {"instanceInfo": [{instanceConfig1}, {instanceConfig2}],
>  "tagInfo": {"tag1": ["localhost_1"]}}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message