Is the underlying disk spinning disk? Because that'd be about right for a
cold read (non cached), the fast reads would likely be in buffer cache or
just pure memtable reads.
On Wed, Dec 24, 2014 at 5:32 AM, nitin padalia
wrote:
> Is merging costly operation with wide rows?
> On Dec 10, 2014 5:53
Is merging costly operation with wide rows?
On Dec 10, 2014 5:53 PM, "nitin padalia" wrote:
> I am using a schema like below:
>
> CREATE TABLE user_location_map (
> store_id uuid,
> location_id uuid,
> user_serial_number text,
> userobjectid uuid,
> PRIMARY KEY ((store_id, loc
I am using a schema like below:
CREATE TABLE user_location_map (
store_id uuid,
location_id uuid,
user_serial_number text,
userobjectid uuid,
PRIMARY KEY ((store_id, location_id), user_serial_number)
) WITH CLUSTERING ORDER BY (user_serial_number ASC)
AND bloom_filter_fp_ch
