I looked into it yesterday, but not sure if it's possible: infra jira search and googling comes up empty. If it's not, one of us could always fork the Helix repository on GitHub and give interested people access.
Broadly, here's what needs to be done in that branch to implement what we discussed in the meeting: 1. Definition of ClusterCommand, ResourceCommand, ParticipantCommand, PartitionCommand 2. New HelixAdministrator interface that leverages those commands 3. Consolidated ZkHelixAdministrator class that merges work done in ZkHelixAdmin, ClusterAccessor, ResourceAccessor, and ParticipantAccessor 4. Builders to support creation of a ZK-based administrator in a pluggable way There also need to be answers for the following questions: 1. Should HelixAdministrator be a subinterface of HelixRole? 2. If we want HelixAdministrator to manage its connection internally, should there be a start/stop method so that we know when to disconnect? If anyone knows about whether or not it's possible to create a contributor branch, let me know. Otherwise, we can move forward with the GitHub strategy. Kanak ---------------------------------------- > Date: Thu, 27 Feb 2014 17:01:17 -0800 > Subject: Admin api next steps > From: [email protected] > To: [email protected] > > Hi, > > What is the next step on Admin api. Should we start working on the apis in > a branch and make sure we covered all the usecases. > > As I think more, it makes a lot of sense to flesh out the admin api's. > These api's define the basic CRUD operations and applicable to all roles > administrator, participant, controller etc > > Should we create a branch in Apache git. I heard there is a way to get non > committer access to specific branches. Does anyone know how to go about it? > > thanks, > Kishore G
