jgoedeke opened a new issue, #57566:
URL: https://github.com/apache/airflow/issues/57566

   ### Apache Airflow version
   
   3.1.1
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When viewing Assets in the Airflow 3.1.1 UI, the context-specific metadata 
attached to assets is not shown anywhere in the UI. For example, if an asset is 
defined with `extra={...}` (see below), this information is not visible in the 
asset event details, asset event list, or any related asset views. This makes 
it difficult for users to see or audit static asset metadata during asset event 
inspection. Only AssetEvent extra is displayed.
   
   ```python
   Asset(
       's3://bucket/mydata.csv',
       extra={'owner': 'Sir Airflow'},
   )
   ```
   
   ### What you think should happen instead?
   
   The UI should display the `extra` dictionary (static asset metadata) 
somewhere in the Assets view, ideally together with other asset details. This 
could be shown as a dedicated section, or grouped with asset information in the 
event card or detail modal. Showing this field would allow users to see static 
asset metadata alongside event-specific metadata (`extra`).
   
   ### How to reproduce
   
   1. Create an asset with `extra={...}`.
   2. Emit one or more asset events for the asset.
   3. Open the Assets view in the Airflow UI.
   4. Observe that the static asset metadata (`extra`) is not displayed 
anywhere.
   
   ### Operating System
   
   docker
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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