Hi all - Moving forward, let's use GitHub Issues over JIRA. It is closer to the code itself and arguably easier to link to and work with the code. I have created an issue based on the JIRA Dimuthu provided for the time being.
Hunter On Mon, Jun 24, 2019 at 8:56 AM DImuthu Upeksha <[email protected]> wrote: > Hi Junkai, > > Thanks for the quick response. I created the ticket [2] as you have asked. > > [2] > > https://issues.apache.org/jira/projects/HELIX/issues/HELIX-817?filter=allopenissues > > Thanks > Dimuthu > > On Mon, Jun 24, 2019 at 11:34 AM Xue Junkai <[email protected]> wrote: > > > Hi Dimuthu, > > > > That's a good feature to support in the future. We dont have plan to > > support it right now. Could you please create a Helix ticket for that? > > > > Best, > > > > Junkai > > > > On Mon, Jun 24, 2019 at 7:59 AM DImuthu Upeksha < > > [email protected]> > > wrote: > > > > > Hi Folks, > > > > > > Currently we can set only one instance group tag for a job. > > > > > > jobCfg.setInstanceGroupTag("INSTANCEGROUPTAG"); > > > > > > Do you have anything planned to support multiple instance group tags > for > > > one job so that the job can be run either in group A or group B? This > is > > > somewhat similar to Node Affinity [1] concept in Kubernetes. > > > > > > [1] https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ > > > > > > Thanks > > > Dimuthu > > > > > > > > > -- > > Junkai Xue > > >
