-
Notifications
You must be signed in to change notification settings - Fork 107
Feature: Use scylladb as C* compatible storage backend #888
Comments
it looks like cassandra recently introduced the realistically, scylla will always lag behind cassandra to some extent and/or it may make sense to use different schemas regardless. For that reason, I think it makes sense to move the schemas out of the source code, and into config files for the store schemas and for the index schemas. we can then have a default variant for cassandra and for scylla (and we could even use different defaults for different versions of cassandra/scylla), also allowing people to easily customize the schemas and have MT create the tables for them, simplifying the deployment. thoughts @woodsaj ? |
👍 |
This sounds good to me. We already handle the keyspace creation outside of metrictank so that we can set the replication settings. |
here's some criteria that I think the feature should implement: (most of these may sound obvious, but just want to have a checklist)
|
I've tried to use scylladb as a cassandra backend, mostly for performance and cost.
The table auto-creation failed with a syntax error related to compression the fix was to manually create the keyspace/keytable with :
and off course i've had to disable the two booleans:
one of the error was
The text was updated successfully, but these errors were encountered: