Support fetch executed tensor data from server #80
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 9 commits
December 27, 2018 15:57
…em&getitem # Conflicts: # mars/web/tests/test_api.py
…_tensor # Conflicts: # mars/deploy/local/tests/test_cluster.py # mars/web/session.py
|
Wonder why local session cannot fetch? |
okay... |
|
Yeah, add an interface to Executor to supply |
wjsi
reviewed
Dec 29, 2018
qinxuye
requested changes
Dec 29, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
Add
session.fetchmethod and check if tensor has been submitted insession.run. ForLocalClusterSessionandweb.Session, they can fetch executed tensor from workers and submit other tensors to cluster. ForLocalSession, fetch is not available, it will run all input tensors whether they have run or not.Related issue number
fixes #17 from the client side, other related fixes may be done with #28