Add `.get_client()` method to Cluster class
See original GitHub issueI’m sitting with @costrouc and he’s typing cluster.get_client()
based on his experience with Dask Gateway. Should we upstream this to dask.distributed.deploy.Cluster
?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
API — Dask.distributed 2022.12.1 documentation
The Client connects users to a Dask cluster. It provides an asynchronous user interface around functions and futures. This class resembles executors in ......
Read more >How To Create an HTTP Client with Core HTTP in Node.js
You will begin by making a GET request, the standard HTTP request to receive data. You will then look at ways to customize...
Read more >projects.zones.clusters.get | Google Kubernetes Engine (GKE)
Install the C# client library by adding a dependency on the relevant ... To execute asynchronously in an async method, replace `request.
Read more >Client Libraries | Kubernetes
This page contains an overview of the client libraries for using the Kubernetes API from various programming languages.
Read more >Cluster Sharding - Documentation - Akka
Shard a clustered compute process across the network with locationally transparent message routing using Akka Cluster Sharding.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree that the mulitple imports isn’t very elegant and would totally support an implementation like I outlined in https://github.com/dask/distributed/issues/6732#issuecomment-1187674320
Mostly the concern that I feel is when writing basic materials I have to ask users to import different things from different libraries.
I remember reading Spark materials and getting confused about the Conf and Session and SQLSession objects that I had to create. The ceremony to get a basic example running felt odd.
Adding
Cluster.get_client
would let us rework our common basic example to the following:Not a big deal. My guess is that it’s less friction for early users. Not a big deal though.