Re: Using job specific Participants in Helix

Hi Junkai That did the trick. Thanks a lot Thanks Dimuthu On 17 Nov 2017 10:32, "Xue Junkai" wrote: Hi Dlmuthu and Kishore, Yes. Task framework does support tagged instance at job level. It can be set in JobConfig for InstanceGroupTag. Also, do not forget to tag the

Re: Using job specific Participants in Helix

Hi Dlmuthu and Kishore, Yes. Task framework does support tagged instance at job level. It can be set in JobConfig for InstanceGroupTag. Also, do not forget to tag the instances. Best, Junkai On Thu, Nov 16, 2017 at 8:50 PM, kishore g wrote: > Hi Dlmuthu, > > You can

Re: Using job specific Participants in Helix

Hi Dlmuthu, You can achieve this by using the tag feature in Helix. For example, to Participants P1, P2 should only handle DataCollecting tasks, you need to do the following - Tag Participant P1 and P2 as "DataCollecting" - When you create a job resource that represents DataCollecting

Re: Using job specific Participants in Helix

Dlmuthu, This explains your need. Could you please point me to the code? I was wondering, where and how are we registering callbacks for the participants? On Thu, Nov 16, 2017 at 7:16 PM, DImuthu Upeksha wrote: > Adding Helix Dev > > Hi Ajinkya > > Thank you for

Re: Using job specific Participants in Helix

Adding Helix Dev Hi Ajinkya Thank you for the explanation. Let me explain my requirement. [1] is the correct task registry configuration in a working participant code. All the transition call backs are registered in this code. The problem here is, we have to bundle binaries of all the tasks

Using job specific Participants in Helix

Hi Devs, I'm working on the technology evaluation to re architecture Apache Airavata task execution framework and Helix seems like a good candidate for that as it has an in built distributed generic workflow execution capability. After going through several tutorials, I tried to implement a