If you were able to generate old data offline, using something like the CQLSSTableWriter class, you can add that to the cluster (either via streaming or nodetool import), that would maintain the TWCS invariant.
That said, with https://issues.apache.org/jira/browse/CASSANDRA-13418 , IF you're comfortable with the safety guarantees there (you only use TTLs, you don't explicitly issue deletes, etc), both of those concerns become much less important. On Thu, Sep 15, 2022 at 8:21 AM Michel Barret <michel.bar...@inovatel.com> wrote: > Hi, > > I want to use TWCS on a cassandra table. Documentation explain 2 > concerns about it: > > In case we mix old and new data "in the traditional write path". > > => How can I create another write path to ensure that my old data aren't > in same sstable than new? > > > If I query old data and that generate a repair. > > => How can I check this and/or ensure don't trigg repair with query? > > > Thank you all for your help > > Have a nice day > >
