takayoshi-makabe opened a new pull request, #71047: URL: https://github.com/apache/airflow/pull/71047
`generate_assets_with_last_event_query()` picked the latest `AssetEvent` per asset using `MAX(id)`. Under concurrent writes to the same asset,the order rows arrive at the database doesn't reliably match the order their timestamps were computed, so a row can get a lower id while carrying a *later* timestamp. `MAX(id)` then surfaces a stale event as "latest," which `/ui/assets` displays, sorts, and filters by. Concurrent writes to the same asset are a known hotspot here (#62501, #69977). `public/assets.py` already resolves the equivalent query correctly, grouping by `MAX(timestamp)` first and using `MAX(id)` only to break exact ties. This mirrors that approach, keeping `AssetEvent` joined directly in the outer query so the existing `last_asset_event_timestamp` sort/filter parameters keep working unchanged. --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) Claude Code --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- 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]
