-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add support for DaskExecutor
#816
Conversation
94892d5
to
9a115cf
Compare
@thesuperzapper this should be it. Please give it a gander for now. I've not tested this outside of this PR yet. |
Signed-off-by: Matthias Tafelmeier <[email protected]>
Define dask executor as component in values and reflect chart dependency in chart config. Signed-off-by: Matthias Tafelmeier <[email protected]>
Reflect new executor type DaskExecutor. Signed-off-by: Matthias Tafelmeier <[email protected]>
Airflow does need the dask scheduler endpoint configured. That is done as for the other config vars via env vars. We also autodetect the dask sub chart release to automate generating the connection string from airflow to the dask cluster. Signed-off-by: Matthias Tafelmeier <[email protected]>
Necessary otherwise we get a dependencies out of sync error. Exact error: "the lock file (Chart.lock) is out of sync with the dependencies file (Chart.yaml). Please update the dependencies" Signed-off-by: Matthias Tafelmeier <[email protected]>
9a115cf
to
84a1520
Compare
Signed-off-by: Matthias Tafelmeier <[email protected]>
@thesuperzapper @gsemet could you please prioritize this up? Thanks! |
This issue has been automatically marked as stale because it has not had activity in 60 days. Thank you for your contributions. Issues never become stale if any of the following is true:
|
DaskExecutor
@cherusk thanks for the PR, but it looks like as of Airflow 2.9.0, the upstream project has decided to stop supporting I understand that will be frustrating! |
What issues does your PR fix?
What does your PR do?
This PR brings about a new Airflow executor backend on Dask/Distributed cluster.
Checklist
For all Pull Requests