Lee-W commented on issue #47163: URL: https://github.com/apache/airflow/issues/47163#issuecomment-2700734151
> I think for def structure_data we have the dag object so it should be straight forward. Thanks for clarification! I'll make change for this one as well. > def get_dependencies we do not have the different dag objects loaded, and would have to issue a db query to fetch all those dags I assume but not really a problem. In the latest change, I changed the dependency_id of asset-related dependencies to asset_id. (not yet pushed) > schedule_asset_references and other type of references are setup at dag parsing time right ? Yes > Indeed in the Dag model we see other type of references schedule_asset_name_references schedule_asset_uri_references schedule_asset_references, what is the difference and which one should we look up ? All of them are asset-related things that will eventually resolved into an asset. I already finish the `get_dependencies` and will change `structure_data` as well -- 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]
