vikrantkumar-max commented on PR #54396:
URL: https://github.com/apache/airflow/pull/54396#issuecomment-3187874240
Thanks for the context! The change I made isn’t aimed at addressing UI
caching behavior directly. Instead, it focuses on improving the backend
computation of per-asset "queued" status and normalizing the data structure
returned to the UI.
Summary of changes:
- Display logic for "X of Y assets":
- Y = total assets relevant to the DAG's asset_expression.
- X = assets with lastUpdate > latestRunAfter (i.e., new events since
last DAG run).
- Introduced SQL-based computation of each asset’s "queued" status using a
LEFT JOIN + MAX(CASE) approach.
- Grouped and normalized the data so:
- Non-queued assets have lastUpdate = None.
- The internal queued field is removed from the final response payload
for clarity.
This is primarily to ensure accurate and clean data rendering in the UI,
independent of UI cache issues. It helps avoid confusion by hiding
backend-specific fields and ensuring that only relevant asset updates are shown
post-run.
Please let me know if i understanding is wrong
--
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]
