cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ZAIDI, ASAD" <>
Subject RE: Duplicates columns which are backed by LIST collection types
Date Thu, 24 Oct 2019 15:36:17 GMT
Have you chosen correct datatype to begin with, if you don’t want duplicates?

Generally speaking:

A set and a list both represent multiple values but do so differently.
A set doesn’t save ordering and values are sorted in ascending order. No duplicates are

A list saves ordering where you append or prepend the value into the list. A list allows duplicates.

From: Muralikrishna Gutha []
Sent: Thursday, October 24, 2019 10:27 AM
Cc: Muralikrishna Gutha <>
Subject: Duplicates columns which are backed by LIST collection types

Hello Guys,

We started noticing strange behavior after we migrated one keyspace from existing cluster
to new cluster.

We expanded our source cluster from 18 node to 36 nodes and Didn't run "nodetool cleanup".
We took sstable backups on source cluster and restored which has duplicate data and restored
(sstableloader) it on to new cluster. Apparently applications started seeing duplicate data
mostly on list backed columns. Below is sstable2json output for one of the list backed columns.

Clustering Column1:Clustering Column2:mods (List collection type


Below is the select statement i would expect Cassandra to return data with latest timestamp
rather it returns duplicate values.

select mods from keyspace.table where partition_key ='1117302' and type='ModifierList' and


Any help or guidance is greatly appreciated.

Thanks & Regards
  Murali K Gutha
View raw message