That was my first reaction too.  Build anew task as a convergence point.

On Wed, Jan 29, 2020, 8:49 PM Reed Villanueva <[email protected]> wrote:

> After some more thought, here is my workaround...
>
> [image: image.png]
> Anyone see any holes with this?
>
>
> On Wed, Jan 29, 2020 at 3:26 PM Reed Villanueva <[email protected]>
> wrote:
>
>> Kamil,
>>
>> One thing about my case is that the next tasks (greens) in each branch
>> should only run if the blue task *in that same branch* completes
>> successfully (should *not care about the success/failure status of the
>> other blue tasks*, only that they have been run). Thus I don't think the
>> ALL_DONE trigger rule will help the greens and ALL_SUCCESS would be too
>> strict.
>>
>> Any ideas for such a thing?
>>
>>
>> On Wed, Jan 29, 2020 at 2:14 PM Kamil Breguła <[email protected]>
>> wrote:
>>
>>> white
>>> blue = [blue_a, blue_b, blue_c]
>>> green = [green_a, green_b, green_c]
>>> yellow = [yellow_a, yellow_b]
>>>
>>> cross_downstream(from_tasks=[white], to_tasks=[blue])
>>> cross_downstream(from_tasks=blue, to_tasks=green)
>>> cross_downstream(from_tasks=green to_tasks=yellow)
>>>
>>> This should create the required network of dependencies between tasks.
>>>
>>> Here is visualization available:
>>> https://imgur.com/a/2jqyqQO
>>>
>>> This is the easiest solution and in my opinion the correct one.
>>> However, if you don't want a dependencies then you can create a new
>>> schedule rule by editing the BaseOperator.deps property.
>>>
>>
> This electronic message is intended only for the named
> recipient, and may contain information that is confidential or
> privileged. If you are not the intended recipient, you are
> hereby notified that any disclosure, copying, distribution or
> use of the contents of this message is strictly prohibited. If
> you have received this message in error or are not the named
> recipient, please notify us immediately by contacting the
> sender at the electronic mail address noted above, and delete
> and destroy all copies of this message. Thank you.
>

Reply via email to