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

Add versioning and schema migration for master catalog #846

Open
senderista opened this issue Aug 15, 2016 · 1 comment
Open

Add versioning and schema migration for master catalog #846

senderista opened this issue Aug 15, 2016 · 1 comment

Comments

@senderista
Copy link
Contributor

We need to allow upgrading existing Myria clusters in-place, including when the catalog schema has changed. This would require adding a version field to the catalog (probably in a singleton table), and adding code accompanying any schema change to upgrade the catalog schema from the previous schema version. I don't think we should support upgrading from versions older than the immediate predecessor.

This should fix issues like #841. @dhutchis @jingjingwang @jortiz16 please comment.

@dhutchis
Copy link
Member

In case it's helpful, this is the command I executed in SQLite to upgrade

ALTER TABLE relation_schema ADD is_indexed INTEGER NOT NULL DEFAULT 0;
ALTER TABLE relation_schema ADD is_ascending_index INTEGER DEFAULT 0;

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

No branches or pull requests

2 participants