potiuk commented on PR #59921: URL: https://github.com/apache/airflow/pull/59921#issuecomment-3700663762
> One more note, in utils.py we're also using some db methods like `DagRun.fetch_task_instances` [here](https://github.com/apache/airflow/blob/cf80ae19840f1d03e16323e7bca819550633db97/providers/openlineage/src/airflow/providers/openlineage/utils/utils.py#L988), but we only call it on scheduler. We're also going to add another call to db [here](https://github.com/apache/airflow/pull/59521/changes#diff-090bdefe8e3de4ab44c24490d0b0df9ff2f9445d2d42126e0ce3476908b804d5R1075) for asset triggered dagruns, also performed only on scheduler. Not sure how this relates to treating sqlalchemy as optional. Not yet. This will come later when we will split (some) providers into two types of providers (maybe they won't be named like that) - we've been disussing it but deferred decision on that to after we complete task isolation and separated core and task-sdk. We iwll have to separate some distributions in two: * executors/ui plugins/scheduler listeners and plugins (installable with airflow-core) * Hooks/Operators/macro plugins etc. (installable with task-sdk) This falls in the same part - part of the current openlineage provider should be a distribution installed with "task-sdk" and part should be another distribution installed with "airflow-core". Later we can even split "airflow-ui" as separate distribution and have 3 types of "providers" -- 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]
