potiuk commented on issue #24279: URL: https://github.com/apache/airflow/issues/24279#issuecomment-1148628174
> @potiuk I could open a PR, but the main reason I opened this issue is that I would hope that someone already knows how the `upstream_failed` status trickles downstream, while I only know the two examples I made above (and there are a larger number of trigger rules). I would also like to understand if there is a solution for the use case I have written above (for which I can put together an example if needed), and if not I would think that there is something missing in the functionality itself. I think if it is not documented, then the only way to check is to look it up in the code. And then person, who has already made a considerable effort to look up is llikely the best to document it. Trying to document it, is likely best way to learn it (especially that you will get maintainer's help with that). There is no "must" here of course - but if you will not do it then it will have to wait for someone who would like to. That's why I marked it as "good first issue" - sounds a good issue for someone who would like to spend their time on digging in. Also you might not understand how open-source works. Issues will get implemented because someone would like to take care about them, not because they are opened. So if your goal was to "create the documentation for it", the most certain way is to implement it by you. Otherwise it will have to wait for someone to pick it up. -- 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]
