I created table using the command:
CREATE TABLE correlated_data (
processing_timestamp bigint,
generating_timestamp bigint,
data text,
PRIMARY KEY (processing_timestamp, generating_timestamp)
) WITH CLUSTERING ORDER BY (generating_timestamp DESC);
When I get data using the command
The clustering column is ordered per partition key.
So if for example I create the following table:
create table desc_test (
id text,
name text,
PRIMARY KEY (id,name)
) WITH CLUSTERING ORDER BY (name DESC );
I insert a few rows:
insert into desc_test (id , name ) VALUES ( '
To the point, Thanks!
On Sun, Jul 15, 2018 at 4:31 PM, shalom sagges
wrote:
> The clustering column is ordered per partition key.
>
> So if for example I create the following table:
> create table desc_test (
>id text,
>name text,
>PRIMARY KEY (id,name)
> ) WITH CLUSTERIN
It also helps to think about it with the token values of the partition key
in place. Assume I have a table "users_by_dept" keyed like this: PRIMARY
KEY ((department),username).
Querying that table with the token function on the partition key looks like
this:
SELECT token(department),department,u
