[jira] [Updated] (HELIX-251) Design participant specification for new language bindings

["Jeff Solanas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HELIX-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Solanas updated HELIX-251:
-------------------------------

    Sprint: Sprint #3 9/9 - 10/1, Sprint #4 10/2 - 10/16  (was: Sprint #3 9/9 - 10/1)

> Design participant specification for new language bindings
> ----------------------------------------------------------
>
>                 Key: HELIX-251
>                 URL: https://issues.apache.org/jira/browse/HELIX-251
>             Project: Apache Helix
>          Issue Type: Task
>            Reporter: Kanak Biscuitwala
>            Assignee: Kanak Biscuitwala
>
> There is interest in implementing a Helix participant in Node.js and Python. We should determine the minimal required implementation required for a functional participant in any language. Currently, the Helix participant does the following:
> - creates an ephemeral node under LIVEINSTANCES when it starts
> - listen to MESSAGES for controller messages (e.g. "start serving this replica" and "drop this replica")
> - update the current state with the result of the command
> We may need to wrap some of this functionality, or we may not. Either way, we should figure out exactly what a participant should do, keeping in mind room for potential redesigns and ensuring that maintenance overhead is not too high.



--
This message was sent by Atlassian JIRA
(v6.1#6144)