The clustering keys determine the sorting of rows within a partition. The partitions within a file are sorted by their token (usually computed by applying the murmur 3 hash to the partition key).
If you are using a version of Cassandra < 3.0, you'll need to maintain your own materialized view tables. On Tue, Jan 12, 2016 at 10:07 PM anuja jain <anujaja...@gmail.com> wrote: > I understand the meaning of SSTable but whats the reason behind sorting > the table on the basis of int columns first.. > Is there any data type preference in cassandra? > Also What is the alternative to creating materialised views if my > cassandra version is prior to 3.0 (specifically 2.1) and which is already > in production.? > > > On Wed, Jan 13, 2016 at 12:17 AM, Robert Coli <rc...@eventbrite.com> > wrote: > >> On Mon, Jan 11, 2016 at 11:30 PM, anuja jain <anujaja...@gmail.com> >> wrote: >> >>> 1 more question, what does it mean by "cassandra inherently sorts data"? >>> >> >> SSTable = Sorted Strings Table. >> >> It doesn't contain "Strings" anymore, really, but that's a hint.. :) >> >> =Rob >> > >
