-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Feat: Add XCom 'Timestamp' and unify task columns #57053
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: Add XCom 'Timestamp' and unify task columns #57053
Conversation
|
Only one comment. I think the next step will be to update the API to add an |
@bbovenzi Thanks for the suggestion regarding the |
8ba4a06 to
6697ff2
Compare
pierrejeambrun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one nit.
6697ff2 to
6f4eb4d
Compare
* feat: Add XCom 'Timestamp' and unify task columns * fix: show task_display_name in XCom table with fallback dash (cherry picked from commit 739681b) Co-authored-by: Anshu Singh <anshu.singh@ksolves.com>
* feat: Add XCom 'Timestamp' and unify task columns * fix: show task_display_name in XCom table with fallback dash
Feat: Enhance XCom table with Timestamp and unified Task column
This PR implements two major enhancements to the XCom table in the Airflow Web UI, addressing the user feedback in Issue #56507.
Background:
The original XCom table lacked critical information (Timestamp) and displayed redundant technical data ('Task ID' alongside 'Task Display Name'). This made the table less user-friendly and difficult to trace XCom creation times.
What this PR does:
Unifies Task Columns: Replaces the separate 'Task ID' and 'Task Display Name' columns with a single 'Task' column.
task_display_name.task_idwhen the display name is not available, ensuring task identification is always possible.Adds Timestamp Column: Introduces the 'Timestamp' column.
Notes:
These changes are focused on UI/UX improvements and do not impact core XCom functionality or data storage.
Fixes #56507
^ 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.