Skip to content

caching location to be non-local #494

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

Open
martindurant opened this issue Dec 7, 2020 · 1 comment
Open

caching location to be non-local #494

martindurant opened this issue Dec 7, 2020 · 1 comment

Comments

@martindurant
Copy link
Member

Proposal to have the target location for file caching to be something other than the local filesystem, e.g., a scratch bucket for initial copy of a dataset from one cloud platform to another.

In parallel, the same_names=True parameter should be changed to allow a certain number of parent filenames to be stored as part of the cached file name.

@scottyhq
Copy link

scottyhq commented Dec 9, 2020

this would be neat, just wanted to point out a use-case where this has come up #476 (comment)

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

No branches or pull requests

2 participants