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

Catalog.save may return futures. #556

Merged
merged 5 commits into from Jan 17, 2019

Conversation

Projects
None yet
1 participant
@rainwoodman
Copy link
Member

rainwoodman commented Jan 15, 2019

Catalog.save may return futures when compute=False

The use case is if we know some columns can be computed more efficiently if they are computed together, then we can do the store operation together.

@rainwoodman

This comment has been minimized.

Copy link
Member Author

rainwoodman commented Jan 16, 2019

It would be great if we can have stalled futures that does not gets scheduled immediately.

rainwoodman added some commits Jan 16, 2019

Create future objects of all columns as one graph.
Since if created as seperate graphs, the compute operation
does not seem to reuse result of duplicated operations.

@rainwoodman rainwoodman merged commit cf76859 into bccp:master Jan 17, 2019

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage increased (+0.009%) to 94.812%
Details

@rainwoodman rainwoodman deleted the rainwoodman:save-future branch Jan 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment