Uh oh!
There was an error while loading. Please reload this page.
Alias task_display_name for EventLogResponse - #55160
Conversation
660d08e to
5a2d4f4CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
09e7e2a to
3c90f03CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pierrejeambrun
left a comment
There was a problem hiding this comment.
Looks good to me. We can merge once other comments are resolved.
pierrejeambrun
commented
Sep 4, 2025
Feel free to resolve comments when they are address so we can merge it @guan404ming (unless there is more work planned here) |
guan404ming
commented
Sep 4, 2025
Sure, let me resolve them. It's currently looks good for me but if TP still have any questions please feel free to let me know. I could help follow up or clarify. Thanks! |
7889406 to
c1dadfbCompareThere was a problem hiding this comment.
That makes me realize (I might be wrong) that we are not eagerly loading that relationship on the get_event_logs endpoint, which means that we are lazily emitting many request when serializing responses right?
We probably want to fix that by adding loading options? (I think we have the same issue for retrieving the dag_display_name, dagmodel will be joined lazyly)
Uh oh!
There was an error while loading. Please reload this page.
4617540 to
ec87997CompareUh oh!
There was an error while loading. Please reload this page.
ec87997 to
81c45f5CompareUh oh!
There was an error while loading. Please reload this page.
* Alias task_display_name for event_logs * Update lazy loading to noload (cherry picked from commit 78b8b3c)
pierrejeambrun
commented
Oct 31, 2025
Manual backport #57609 |
Related Issue
#46730
How
task_display_nameforEventLogResponse^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.