Hi Ramzi, all, +1 on this feature. I am evaluating adopting airflow and intend to run partitioned-asset Dags for use cases where restated data for already-processed partitions is routine. The proposed modes and opt-in seem right to me. I have no strong feelings on the implicit default when a user opts-in. This is my first interaction with the project but as there is no activity on this thread perhaps opening a PR would get traction? This feature may be light enough to not require one. Some thoughts on implementation:
1. Concurrency. I had planned to propose this already but a per-partition-key active-run limit, like the Dag-wide max_active_runs, would be useful, e.g. with NewRun should a re-fire wait for an in-flight run of the same partition to finish? 2. Performance. Does the DB have the right indices to support the new query patterns? Thanks, Jack On 2026/09/16 07:54:20 Ramzi Alashabi wrote: > Bumping this. > ________________________________ Your Personal Data: We may collect and process information about you that may be subject to data protection laws. For more information about how we use and disclose your personal data, how we protect your information, our legal basis to use your information, your rights and who you can contact, please refer to: www.gs.com/privacy-notices<http://www.gs.com/privacy-notices>
