Really excited to see this hit the ML James.
As author of the base CDC (get your stones ready for throwing :D) and someone
moderately involved in the CEP here, definitely welcome any questions. CDC is a
*thorny* *problem *in a multi-replica distributed system like this.
On Fri, Sep 27, 2024, at
Hi everyone,
Wiki:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-44%3A+Kafka+integration+for+Cassandra+CDC+using+Sidecar
We would like to propose this CEP for adoption by the community.
CDC is a common technique in databases but right now there is no
out-of-the-box solution to do thi
Thanks all for the work on this epic!
Is there an implementation summary guide similar to guide_8099.md [1] that
can help reviewers not involved with the effort navigate through the code ?
It would be great to have it if this is not already available or being
planned. There's a similar one though
Hi,
Can we make some schema adjustments to System.compaction_history table to
meet our needs?
For example : If there is no task execution, what about just recording 0
bytes_in, 0 bytes_out for this compaction history . Other status can be
placed in compaction_properties,
and you can even add a c
Thank you Maxim for summarizing it like this for better visibility of what
you are suggesting to contribute.
I am OK with that in general but:
1) The table should be limited in its size (I think the original patch you
had was already done with space-limitation in mind). Since we want to put
this
Hello everyone,
I still need a few more eyes on [1][2], but this time I'm going to try
and do some marketing for the feature I'm talking about, so...
We are trying to bridge the gap between the API that is called and the
compaction process that MAY or MAY NOT be called as a result, and make
user
+1
On Fri, Sep 20, 2024 at 4:37 PM Mick Semb Wever wrote:
>
> Proposing the test build of Cassandra 5.0.1 for release.
>
> sha1: c206e4509003ac4cd99147d821bd4b5d23bdf5e8
> Git: https://github.com/apache/cassandra/tree/5.0.1-tentative
> Maven Artifacts:
> https://repository.apache.org/content/rep
If you exclude test changes, there’s < 50k added and ~2k removed. This works
out to ~7% of the scale of 8099 for lines modified, if this is the benchmark
for disruption.
Altogether, this is a very small patch from the perspective of the existing
codebase. Probably doesn’t even come close to the
