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" a écrit :
> oh.. the difference between the the ONE field and the remaining 29 is
> massive.
>
> I
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 wrote:
> Don't forget that when you do the Select with limit set to 100
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 incrementally
Good idea, bytes are merely processed by the server so you're saving a lot
of Cpu. AFAIK getBytes should work fine.
Le 24 juin 2014 05:50, "Kevin Burton" a écrit :
> I'm building a webservice whereby I read the data from cassandra, then
> write it over the wire.
>
> It's going to push LOTS of con
With the Java Driver, set the fetchSize and use ResultSet.iterator
Le 24 juin 2014 01:04, "ziju feng" a écrit :
> Hi All,
>
> I have a wide row table that I want to iterate through all rows under a
> specific partition key. The table may contains around one million rows per
> partition
>
> I was
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 ord
I'm building a webservice whereby I read the data from cassandra, then
write it over the wire.
It's going to push LOTS of content, and encoding/decoding performance has
really bitten us in the future. So I try to avoid transparent
encoding/decoding if I can avoid it.
So right now, I have a huge
Hi All,
I have a wide row table that I want to iterate through all rows under a
specific partition key. The table may contains around one million rows per
partition
I was wondering if the default 1 rows LIMIT applies to automatic
pagination in C* 2.0 (I'm using Datastax driver). If so, what i
The semantics of "null" is encoded at the protocol side, all you can do is
trying to tweak at client side to handle "null" semantics correctly with
regards to your business
On Mon, Jun 23, 2014 at 8:34 PM, Robert Coli wrote:
> On Sat, Jun 21, 2014 at 11:17 AM, Kevin Burton wrote:
>
>> AH! tha
On Sat, Jun 21, 2014 at 11:17 AM, Kevin Burton wrote:
> AH! that makes sense then… so second time around, when you write null,
> you're actually writing a tombstone, then during the next compaction, less
> data will be stored and the value will be removed.
>
> Makes sense! Not sure why I didn't
On Sun, Jun 22, 2014 at 11:36 AM, Jack Krupansky
wrote:
> And that leaves open the possibility that this feature may have a bug.
>
General feedback on the idea that Secondary Indexes might have a bug :
http://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201405.mbox/%3CCAEDUwd1i2
Thank you all,
The issue was resolved (or more exactly bypassed) by adding small python
script running hourly in cron on 1-2 nodes, which pre-provision next hour
keyspace. One hour is definitely enough time for scheme propagation.
Regards,
Pavel
On Sun, Jun 22, 2014 at 9:35 AM, Robert Stupp
On Mon, Jun 23, 2014 at 6:19 PM, James Campbell <
ja...@breachintelligence.com> wrote:
> Huilang,
>
>
> Since there hasn't been another reply yet, I'll throw out an idea that
> worked for us as part of a test, though it does not seem exactly like a
> "preferred" way since it crosses code-bases.
Huilang,
Since there hasn't been another reply yet, I'll throw out an idea that worked
for us as part of a test, though it does not seem exactly like a "preferred"
way since it crosses code-bases. We built the type using straight java type,
then used the Datastax v2 driver's DataType class s
Anyone has any clue of what is happening in our cluster with the given
information?
What other informations could help you to help me :-D ?
2014-06-18 21:07 GMT+02:00 Robert Coli :
> On Wed, Jun 18, 2014 at 5:36 AM, Alain RODRIGUEZ
> wrote:
>
>> We stop the node using : nodetool disablegossi
15 matches
Mail list logo
