amoghrajesh opened a new pull request, #68395:
URL: https://github.com/apache/airflow/pull/68395

   …wrote it
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   For user-facing UI changes, please attach before/after screenshots (or a 
short
   screen recording) so reviewers can assess the visual impact.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [x] Yes: claude sonnet
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   
   ---
   
   ### What
   
   The Asset Store table had no visibility into what wrote each entry. When a 
task updates an asset store value via the execution API, there was no way to 
trace which task instance was responsible from the UI.
   
   ### Current behaviour
   
   The Asset Store table shows key, value, and updated-at timestamp but no 
information about what wrote the entry.
   
   ### Proposed change
   
   Adds a "Last Updated By" column to the Asset Store table. When an entry was 
written by a task, it renders the task ID as a clickable link to the task 
instance page (`/dags/{dag_id}/runs/{run_id}/tasks/{task_id}`) with the Dag ID 
shown as a muted subtitle. Mapped task instances link to the mapped variant 
path. API and watcher writes show plain "API" or "Watcher" text.
   
   ### Changes of Note
   
   The `AssetStoreWriterKind` enum values in the OpenAPI-generated types are 
lowercase (`'task' | 'watcher' | 'api'`), matching what the API returns. 
Comparisons must use lowercase string literals accordingly.
   
   ### Some screenshots
   
   <img width="1783" height="1049" alt="image" 
src="https://github.com/user-attachments/assets/c17abc0b-e485-40bf-94e0-2fd42686a0ae";
 />
   
   Clicking on the link leads to TI logs page
   
   <img width="1783" height="1049" alt="image" 
src="https://github.com/user-attachments/assets/0403d7be-014a-465d-9a58-e24aff14d623";
 />
   
   
   
   ---
   
   * 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]

Reply via email to