Skip to content

Conversation

DavidKatz-il
Copy link
Contributor

Support executing on more dask-clusters (e.g. yarn).
Solving this issue.

Copy link
Contributor

@natekupp natekupp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See one comment, take a look and I'll get this landed tomorrow.

Thanks again for taking this on!

base on discussion in PR
edit docstring.
@natekupp
Copy link
Contributor

natekupp commented May 22, 2020

Great—I kicked off a Buildkite build here: https://buildkite.com/dagster/dagster/builds/12891

A few follow-ups from that:

@natekupp natekupp merged commit 16fb929 into dagster-io:master May 26, 2020
@DavidKatz-il DavidKatz-il deleted the add-dask-client-type branch May 26, 2020 16:54
alangenfeld added a commit that referenced this pull request Oct 28, 2020
Summary:
This is a capability we advertise in the docs that was removed in #2498, I think on accident.

The top level `Client` object in dask takes either a `Cluster` object - which all the existing config schema is used to control, or just a string indicating the address of a running scheduler https://distributed.dask.org/en/latest/client.html

I also cleaned up false advertising about python 2 support since dask does not run on py2

Test Plan: new test

Reviewers: nate, max, sandyryza

Reviewed By: nate

Differential Revision: https://dagster.phacility.com/D4925
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants