No longer use COMPACT STORAGE for Cassandra 3+ with CQL backend#1135
Merged
pluradj merged 1 commit intoJanusGraph:0.2from Jul 9, 2018
Merged
No longer use COMPACT STORAGE for Cassandra 3+ with CQL backend#1135pluradj merged 1 commit intoJanusGraph:0.2from
pluradj merged 1 commit intoJanusGraph:0.2from
Conversation
Fixes JanusGraph#1023 Signed-off-by: Jason Plurad <pluradj@us.ibm.com>
sjudeng
approved these changes
Jul 6, 2018
Contributor
sjudeng
left a comment
There was a problem hiding this comment.
Very nice. All code updates are covered by tests. Also compared new (cql) config files with existing (cassandra) variants and updates were as expected.
10 tasks
This file contains hidden or 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
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.
Fixes #1023
Signed-off-by: Jason Plurad pluradj@us.ibm.com
Thank you for contributing to JanusGraph!
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
master)?For code changes:
For documentation related changes:
[skip ci]tag to the first line of your commit message to avoid spending CPU cycles in
Travis CI when no code, tests, or build configuration are modified?
Note:
Please ensure that once the PR is submitted, you check Travis CI for build issues and submit an update to your PR as soon as possible.