Hi Aaron,
On 23/12/12 20:18, aaron morton wrote:
First, the non helpful advice, I strongly suggest changing the data
model so you do not have 100MB+ rows. They will make life harder.
I don't think we have 100MB+ rows. Column families, yes - but not rows.
Write request latency is about 900
On 21/12/12 17:56, Yiming Sun wrote:
James, you could experiment with Row cache, with off-heap JNA cache, and
see if it helps. My own experience with row cache was not good, and the
OS cache seemed to be most useful, but in my case, our data space was
big, over 10TB. Your sequential access pa
>
> CREATE TABLE seen_ships (
>day text,
>time_seen timestamp,
>shipname text,
>PRIMARY KEY (day, time_seen)
>);
In CQL3, we could select all the columns with the same 'day' and same
'time_seen'.
Is it possible with cassandra-cli?
On Mon, Dec 24, 2012 at 6:5
