nathadfield commented on PR #71074: URL: https://github.com/apache/airflow/pull/71074#issuecomment-5830267041
Hello! We are encountering this issue and have been able to reproduce it on current main with PostgreSQL 14 and a single scheduler. The reproduction has two parallel producer tasks emitting different assets for the same partition, and a consumer using PartitionedAssetTimetable with AssetAll(A, B) . Both tasks succeeded about 0.3 ms apart, but their events ended up on separate pending APDRs, each with one asset. No consumer run was created. The source and mapped partition keys match exactly, so this isn’t a partition-key mismatch or the multiple-scheduler duplicate-run issue. We also reproduced it deterministically using two real transactions calling register_asset_change() , synchronized so both APDR lookups finish before either inserts. The trace confirms they lock different asset rows. Sequential A/B registration and concurrent same-asset registration both converge on one APDR. Is there still a plan to refresh this PR? Happy to share the reproduction and help validate the updated approach rather than open a duplicate. -- 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]
