Skip to content
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

Allow multiple stores in Dataverse #6485

Closed
qqmyers opened this issue Jan 6, 2020 · 0 comments · Fixed by #6488
Closed

Allow multiple stores in Dataverse #6485

qqmyers opened this issue Jan 6, 2020 · 0 comments · Fixed by #6488

Comments

@qqmyers
Copy link
Member

qqmyers commented Jan 6, 2020

For use cases in which it makes sense for data files to be stored in more than one location (such as keeping sensitive data local, providing different types of stores for different data sizes, enabling multiple stakeholders to contribute storage behind a Dataverse instance, allowing new files to go to s3 without moving existing files from a local file store), it would be useful for Dataverse to support configurations with more than one store enabled.
I'm preparing a PR based on work for TDL that provides such support. It implements the core capability for Dataverse to reference files in multiple locations, supports backward-compatibility (requires some config changes but no database changes or need to move files), and provides a mechanism to specify a default store and to associate a store with a Dataverse (so that all datasets within that Dataverse use the specified store.).

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

Successfully merging a pull request may close this issue.

1 participant