bbovenzi commented on pull request #22272:
URL: https://github.com/apache/airflow/pull/22272#issuecomment-1069351761


   > * `/success` and `/failed` set state to a task (and potentially its 
upstreams/downstreams). It feels a bit weird to be able to set the state to 
only one mapped task? Also upstream/downstream makes less sense if any of those 
are mapped. So I’m currently leaving these views alone (i.e. setting 
success/failed to a mapped task sets the state of all mapped tis). We can 
perhaps add some UI components to optionally do more fine-grained state 
modification.
   
   I think leaving it alone is fine, as long as the confirmation screen still 
works. 
   
   We will want to select individual mapped tasks too. I'm not sure if enabling 
that is also in scope of this PR or a later task. But we probably want to allow 
only past/future of that exact map_index and disable upstream/downstream 
options.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to