fix(db) support for cassandra 4 #3873
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The schema selection based on cassandra major_version of 3 assumes future versions uses the same schema. Datastax Enterprise 6.X reports release_version in system.local table as 4.0.X Issue Kong#3837
mprimeaux
approved these changes
Oct 19, 2018
thibaultcha
approved these changes
Oct 22, 2018
|
Thanks! Manually merged with a few minor tweaks (updated a missing location). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Kong 014.0 fails to start when backed by Datastax Enterprise 6.X with error
could not load routes: [Invalid] table schema_columns does not existDSE 6.X reports 4.0.X as the release_version in system.local table. The system schema components used by Kong in 3 are the same in 4 so changes were made such that schema selection based on cassandra major_version assumes future versions use the same schema.
Issues resolved
Fix #3837