uranusjr commented on PR #67637: URL: https://github.com/apache/airflow/pull/67637#issuecomment-5260028067
I think the idea of _an event that signifies a dag run’s end_ makes sense. The main reason behind this is if you have a bunch of leaf tasks (say `a >> [b >> c, d >> e >> f, g, h]`, you’d need a catch-all task at the end of every leaf (`[c, f, g, h] >> z`), which not only looks bad in the graph (this is admittedly petty), but also is difficult to maintain if you edit the workflow. However, I do wonder if there’s a good way to do this. Maybe what we should do is not to create a special kind of asset event (that associated to a dag instead of task), but a special way to define a task that always runs at the end of a dag (except teardowns) to collect the results. (I also wonder if this ties into `@result`.) -- 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]
