+1 nb Great to see this get worked on.
> On Sep 28, 2026, at 6:36 PM, Blake Eggleston <[email protected]> wrote: > > > +1 > >> On Mon, Sep 28, 2026, at 4:15 PM, Andy Tolbert wrote: >> +1, I'm really interested in the goals of this CEP and would like to help >> contribute in any way that I can (review, testing, etc.). >> >> Thanks, >> Andy >> >> On Mon, Sep 28, 2026, at 8:40 PM, Chris Lohfink wrote: >> > I'd like to call a vote on CEP-66: Zero-copy SSTable splitting. >> > >> > The proposal splits eligible compressed SSTables by reusing their >> > encoded compression chunks and rebuilding the child components, >> > avoiding a row rewrite. It starts with an opt-in sstablesplit >> > --zero-copy mode for split tool and BIG-format SSTables on Cassandra >> > 7.0/trunk. Reflinks provide an additional optimization where supported; >> > otherwise, Cassandra copies the encoded bytes. Follow-up incremental >> > phases cover Spark support, anticompaction, BTI, 2i, and partial-range >> > zero copy streaming. >> > >> > The discussion covered the new SSTable format, compatibility, reflink >> > complexity, and digest generation. The proposal and discussion are here: >> > >> > Proposal: >> > https://cwiki.apache.org/confluence/spaces/CASSANDRA/pages/451972773/draft+CEP-66+Zero-copy+SSTable+splitting >> > >> > >> > Discussion: >> > https://lists.apache.org/thread/sjqbv0m451kqopms8whymgwbrr2v16tw >> > >> > Please cast your vote in this thread. The vote will remain open for at >> > least 72 hours, longer if needed. Per the CEP process, adoption >> > requires three binding +1 votes and no binding vetoes. >> > >> > Thanks, >> > Chris >>
