You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: