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 forward compatibility check to updater #111

Merged
merged 1 commit into from
Feb 5, 2018

Conversation

pluehne
Copy link
Contributor

@pluehne pluehne commented Feb 5, 2018

With this addition, the updater checks the schema version of the data in the data repository before attempting to run. In the case that the schema is outdated, an error is returned indicating that a migration
needs to be performed manually.

Additionally, the new script check-schema.py can be manually invoked to check the data schema prior to actually running the updater.

@pluehne pluehne self-assigned this Feb 5, 2018
@pluehne pluehne force-pushed the patrick/forward-compatibility-check branch 4 times, most recently from 4a5a26d to 51ec1cf Compare February 5, 2018 16:20
@pluehne
Copy link
Contributor Author

pluehne commented Feb 5, 2018

@larsxschneider: Ready for review 😄.

With this addition, the updater checks the schema version of the data in
the data repository before attempting to run. In the case that the
schema is outdated, an error is returned indicating that a migration
needs to be performed manually.

Additionally, the new script “check-schema.py” can be manually invoked to
check the data schema prior to actually running the updater.
@pluehne pluehne force-pushed the patrick/forward-compatibility-check branch from 51ec1cf to 9d3b0e0 Compare February 5, 2018 17:06
@larsxschneider larsxschneider merged commit 4411496 into master Feb 5, 2018
@larsxschneider larsxschneider deleted the patrick/forward-compatibility-check branch February 5, 2018 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants