blag commented on issue #35297: URL: https://github.com/apache/airflow/issues/35297#issuecomment-1843376925
Respectfully, I believe this issue is invalid. Datasets and dataset events are separate and distinct things, as are their respective `extra` fields, and copying `DatasetModel.extra` into each and every `DatasetEvent.extra` field breaks both the original intent of both and database normalization. If you are quite sure that you want to access `DatasetModel.extra` within a task, you should be able to query the Airflow database directly from within the task, using the keys available in `triggering_dataset_events`. However, you should think quite a lot about whether or not this is the best way to do what you are trying to do, including what complications can arise with this, before you embark down that road. It may be the case that simply adding a parameter to your DAG is a better solution. Without more details about your specific use case, it's impossible to give better guidance either way. -- 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]
