Thanks for bringing this out!
My first question when quickly looking at this is can we make the
CompressionInfo change agnostic to the algorithm or have the format change
based off the algorithm? Lz4 has similar (though not as easy to use as zstd)
feature and new algorithms might come out whic
Hi community,
We would like to propose *CEP-54: ZSTD Compression with Dictionary Support*
for adoption by the community:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-54%3A+ZSTD+with+Dictionary+SSTable+Compression
This CEP proposes introducing ZSTD with dictionary compression for
SSTa
Hi Andres,
This looks like a great CEP. Having official, source-controlled code within
Cassandra (or a sidecar in this case) to handle common operator actions would
centralize best practices and make the operator experience smoother—especially
for users who may not have deep Cassandra expertise
Thanks for the CEP! It fills the gaps of CEP-40 as well.
A small question from my side: I see that the underlying assumption is that
Sidecar is able to query Cassandra instances before bouncing/recognizing
the bounce. What if it could not communicate with the Cassandra instance
(e.g., binary proto
