I’ll answer them in the DISCUSS thread so the technical discussion stays together.
Chris On Thu, Oct 1, 2026 at 5:08 PM Benedict Elliott Smith <[email protected]> wrote: > Hi Chris, > > Did you miss my email[1] on the DISCUSS thread? Abe partially responded to > it, and I found his answer to this part satisfactory, but I would > appreciate discussing the remaining items before we move to a VOTE. > > Thanks > > https://lists.apache.org/thread.html/07c52dv46xk4hynknfb42kkh424r3o1y > > On 2026-09-28 20:40 UTC 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 > > < > https://cwiki.apache.org/confluence/spaces/CASSANDRA/pages/451972773/draft+CEP-66+Zero-copy+SSTable+splitting > > > > > > Discussion: > > https://lists.apache.org/thread/sjqbv0m451kqopms8whymgwbrr2v16tw > > <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 > > >
