ninsbl commented on issue #55200: URL: https://github.com/apache/airflow/issues/55200#issuecomment-4766207666
In my setup, I use Asset.extra quite extensive to centralize some metadata for an asset This is both metadata for human consumers (like e.g. description, ...). But also metadata ment to be used in processing (like where the Asset files are stored, versions, related service URLs, ...). That way I do not have to define that kind of metadata in DAG code, but rather get it from the asset itself, and I have a pydantic model for required asset.extra content in my DAGs. So, to me Asset.extra seems quite understandable and actually very useful. -- 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]
