[
https://issues.apache.org/jira/browse/HELIX-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Francois Im updated HELIX-590:
-----------------------------------
Attachment: helixadmin-void-return.patch
This patch makes some of the methods that had no return codes before return a
boolean, so that client code can retry calls that did not succeed.
> HelixAdmin API does not return status codes
> -------------------------------------------
>
> Key: HELIX-590
> URL: https://issues.apache.org/jira/browse/HELIX-590
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Jean-Francois Im
> Attachments: helixadmin-void-return.patch
>
>
> Many of the HelixAdmin methods return void, even though the underlying ZK can
> fail. There is no way through the HelixAdmin API to determine if a write
> failed due to having multiple concurrent writers to the same ZK node.
> For example, calling HelixAdmin.setResourceIdealState() internally calls
> accessor.setProperty, which returns either true or false depending on whether
> or not the write was successful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
