does come down to how you will be accessing the data – query,
view, update.
-- Jack Krupansky
From: Donald Smith
Sent: Wednesday, March 26, 2014 1:22 PM
To: mailto:user@cassandra.apache.org
Subject: Question about how compaction and partition keys interact
In CQL we need to decide between using
ys a date.
>
>
>
> Thanks, Don
>
>
>
> *From:* Jonathan Lacefield [mailto:jlacefi...@datastax.com]
> *Sent:* Wednesday, March 26, 2014 11:20 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Question about how compaction and partition keys interact
>
Don
From: Jonathan Lacefield [mailto:jlacefi...@datastax.com]
Sent: Wednesday, March 26, 2014 11:20 AM
To: user@cassandra.apache.org
Subject: Re: Question about how compaction and partition keys interact
Don,
What is the underlying question? Are trying to figure out what's going to be
fa
Don,
What is the underlying question? Are trying to figure out what's going
to be faster for reads or are you really concerned about storage?
The recommendation typically provided is to suggest that tables are
modeled based on query access, to enable the fastest read performance.
In your
In CQL we need to decide between using ((customer_id,type),date) as the CQL
primary key for a reporting table, versus ((customer_id,date),type).
We store reports for every day. If we use (customer_id,type) as the partition
key (physical key), then we have a WIDE ROW where each date's data is s
