cmarteepants commented on issue #44336: URL: https://github.com/apache/airflow/issues/44336#issuecomment-5732589023
Also, thanks for raising the convo and questions here rather just opening a PR. We need more of that :) For context on where I'm coming from: this would be the third overlapping run-concurrency control on a DAG alongside `max_active_runs` and `Backfill.max_active_runs`, and params like that are hard to walk back once released. The asset-triggered question makes me think the semantics are broader than they look. Although I could go either way, my instinct was the opposite of Jake's, and I can see some people wanting to include it and some wanting to exclude it. Which is why I'm curious about the timetable path. If it can extended to express what you need, it keeps this available to the people who want it and would allow you to tune it to your use-case without adding surface area for everyone else. -- 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]
