-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Define ScyllaDB as drop-in replacement for Cassandra #4353
Define ScyllaDB as drop-in replacement for Cassandra #4353
Conversation
i can provide a demo docker-compose file but have no idea where to place it to make it easily discoverable by the community |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can add a folder plugins/storage/scylladb with a README and a docker-compose file. The README can call out any relevant details (or any differences vs. Cassandra). But I would like to have a clear disclaimer at the top that this is not an officially supported backend, meaning that we will not proactively address any issues that may arise from incompatibilities between the two databases (we may still accept PRs).
Please make sure all commits are signed (or squash into one and sign). |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #4353 +/- ##
==========================================
- Coverage 97.10% 97.10% -0.01%
==========================================
Files 300 300
Lines 17697 17697
==========================================
- Hits 17185 17184 -1
- Misses 412 413 +1
Partials 100 100
Flags with carried forward coverage won't be shown. Click here to find out more. see 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, but please make sure commits are signed (see CONTRIBUTING.md)
|
||
#### Protocol version | ||
|
||
Jaeger server detects Cassandra protocol version automatically. At the date of the demo with specified versions server detects that it connected via protocol version 3 while it is actually 4. This leads to warn log in cassandra-schema container: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like maybe there should be a config param in Jaeger to set the version explicitly instead of sniffing it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i have tried both
CASSANDRA_PROTOCOL_VERSION: 4
CASSANDRA_VERSION: 4
but nothing helped. It depects the version from interaction with ScyllaDB
Signed-off-by: Maxim Korolyov <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: Maxim Korolyov <[email protected]> Signed-off-by: Maxim Korolyov <[email protected]>
Signed-off-by: Maxim Korolyov <[email protected]>
Signed-off-by: Maxim Korolyov <[email protected]>
769b6a4
to
bfbace7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few small improvements
Signed-off-by: Maxim Korolyov <[email protected]>
Hi @yurishkuro I still use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. One possible minor improvement is to pull the Jaeger and ScyllaDB versions into variables at the top of the compose file.
Which problem is this PR solving?
Defines that Jaeger server supports ScyllaDB as a storage backend as a drop-in replacement for Cassandra
Short description of the changes
Updated README.md