dask / dask/distributed

ActorFuture roadmap

Open
#2,950 9 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

Hi!

Currently `ActorFuture`s are not really Futures, but just a caching mechanism.
As explained here: https://distributed.dask.org/en/latest/actors.html#call-remote-methods,
> They can’t be placed into additional submit or map calls to form dependencies.

For my use case, I want to have a dag, in which every part of the dag is persistent. So I need to pass the output of 1 part of the dag (=`ActorFuture`) as a parameter to the submit call of the next part. Unfortunately this is not possible yet. `TypeError: ('Could not serialize object of type ActorFuture.', '')`
(I know in similar projects like Ray, this is possible).
I was wondering if someone knows what the plans with Dask Actor(Future)s are?
Will ActorFuture be fully featured Futures soon or..?

Thanks for helping! Pj

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.