That scheme assumes we have to read counter value before write something to the timeline. This is what we try to avoid as an anti-pattern.
By the way, is there any difference between slice trimming of one row and sharding pattern in terms of compaction? AFAIK, delete with timestamp by primary key also creates single row tombstone. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/disk-space-and-tombstones-tp7596356p7596367.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
