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.

Sign up for GitHub

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

Jump to bottom

[general] How should we evolve the Imports API? #14

Open
chrismetcalf opened this issue Apr 18, 2016 · 1 comment
Open

[general] How should we evolve the Imports API? #14

chrismetcalf opened this issue Apr 18, 2016 · 1 comment
Labels
question

Comments

@chrismetcalf
Copy link
Contributor

This thread will serve as a discussion and feedback thread about what we should take into consideration as we design and build a replacement for the Import API.
@kevinsmgov
Copy link

It would be handy to leave the v2.0 version of a dataset in production while testing updates on v2.1. Also, if a dataset has a number of views, it would be nice to be able to migrate them instead of having to recreate from scratch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrismetcalf @kevinsmgov