Titan with Cassandra CQL #364
Open
Conversation
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
ghost
assigned
Member
|
We have been keeping an eye on Cassandra's support for thrift and it is clear that things are moving in the direction of CQL. That said, there are some features that make it appealing to use thrift for now (less overhead, multi_slice_get). |
|
Any news on CQL support? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
This is the current implementation of CQL support (#312). There are failing unit tests, mostly caused by latest changes in Titan core, that I did not yet implemented.
Some refactoring is still required.
I will continue to push my work to this pull request.
Any comments/suggestions are welcome.
I have tried to use same data model, replacing wide rows with cql equivalent, that is table with compound primary key.