Re: Getting all unique keys

Thanks Christophe, we didn't want to add too many moving parts but is sound like a good solution. do you have any reference / link that I can look at ? Cheers Avi On Mon, Aug 21, 2017 at 3:43 AM, Christophe Schmitz < christo...@instaclustr.com> wrote: > Hi Avi, > > Have you thought of using Spar

Re: Getting all unique keys

Hi Avi, Have you thought of using Spark for that work? If you collocate the spark workers on each Cassandra nodes, the spark-cassandra connector will split automatically the token range for you in such a way that each spark worker only hit the Cassandra local node. This will also be done in parall

Re: Moving all LCS SSTables to a repaired state

Correction: Full repairs do mark SSTables as repaired in 2.2 (CASSANDRA-7586 ). My mistake, I thought that was only introduced in 3.0. Note that if mixing full and incremental repairs you probably want to be using at least 2.2.10 because of CASS

Re: Getting all unique keys

Thank you very much , one question . you wrote that I do not need distinct here since it's a part from the primary key. but only the combination is unique (*PRIMARY KEY (id, timestamp) ) .* also if I take the last token and feed it back as you showed wouldn't I get overlapping boundaries ? On Sun,

Re: Getting all unique keys

You should be able to fairly efficiently iterate all the partition keys like: select id, token(id) from table where token(id) >= -9204925292781066255 limit 1000; id | system.token(id) +-- ...

Re: Moving all LCS SSTables to a repaired state

Pretty much, I wouldn't set your heart on having 0 unrepaired SSTables.