anishgirianish commented on issue #67368: URL: https://github.com/apache/airflow/issues/67368#issuecomment-4530013252
> [@anishgirianish](https://github.com/anishgirianish) took me some time to think about it. But this is what I'm thinking. let me know what do you thing 🙂 @Lee-W Thank you so much for writing this up. The provenance vs. routing split really makes sense to me. Couple of small thoughts: - I completely agree on dropping the back-fill. Only thing I'd love to keep is the "this run handled partition X" view — we could pull that from the AssetEvents instead, maybe as a small follow-up. - On the manual-pk reject: I was poking around the trigger paths and got a little curious how you're picturing it landing. Looks like the public UI/REST trigger goes through create_dagrun directly while CLI/exec-API go via _trigger_dag, and create_dagrun is also where the scheduler/backfill set partition_key legitimately. Were you thinking one gated spot, or a check per path? Just want to make sure the UI trigger gets caught too. - +1 on the warn-and-ignore for alias add_partitions, and on rejecting for partitioned_at_runtime. I'd be glad to pick this up and work through it. Thanks again! -- 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]
