oh.. the difference between the the ONE field and the remaining 29 is
massive.
It's like 200ms for just the 29 columns.. adding the extra one cause it to
timeout .. 5000ms...
On Mon, Jun 23, 2014 at 10:30 PM, DuyHai Doan doanduy...@gmail.com wrote:
Don't forget that when you do the Select
Yes but adding the extra one ends up by * 1000. The limit in CQL3 specifies
the number of logical rows, not the number of physical columns in the
storage engine
Le 24 juin 2014 08:30, Kevin Burton bur...@spinn3r.com a écrit :
oh.. the difference between the the ONE field and the remaining 29 is
Can you do you query in the cli after setting tracing on?
On Mon, Jun 23, 2014 at 11:32 PM, DuyHai Doan doanduy...@gmail.com wrote:
Yes but adding the extra one ends up by * 1000. The limit in CQL3
specifies the number of logical rows, not the number of physical columns in
the storage engine
I have a table with a schema mostly of small fields. About 30 of them.
The primary key is:
primary key( bucket, sequence )
… I have 100 buckets and the idea is that sequence is ever increasing.
This way I can read from bucket zero, and everything after sequence N and
get all the writes
Don't forget that when you do the Select with limit set to 1000, Cassandra
is actually fetching 1000 * 29 physical columns (29 fields per logical
row).
Adding one extra big html column may be too much and cause timeout. Try to:
1. Select only the big html only
2. Or reduce the limit
