Hi Oskar, My guess (wait for confirmation maybe): When you read from a primary key + specific clustering key or (range of clustering keys), Apache Cassandra will look for these specific values and not read all the row. Yet it is important to know that a minimal block size of 64 KB is read from the disk (not configurable in C* 2.0). Or if the table is compressed, the minimal read size is a chunk, for which you can manually set the size. That's why when using small rows, it is sometimes interesting to enable compression, even if you don't care about the data size... This all has been improved a bit in 2.1 / 2.2 and greatly in C* 3.0+.
I might write a post about this, if I do, I will let you know. It's an interesting topic I have been working on recently. C*heers, ----------------------- Alain Rodriguez - @arodream - al...@thelastpickle.com France The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com 2017-04-21 10:44 GMT+02:00 Oskar Kjellin <oskar.kjel...@gmail.com>: > If I have a table like this: > > PRIMARY KEY ((userid),deviceid) > > And I query > SELECT * FROM devices where userid= ? and deviceid = ? > > Will cassandra read the entire partition for the userid? So if I lots of > tombstones for userid, will they get scanned? > > I guess this depends on how the bloomfilter is working. Does it contain > partitioning key or primary key? > > We're using 2.0.17 if it matters. > > /Oskar >
