Re: Partition size

2016-09-09 Thread Jonathan Haddad
I fully agree with Benedict here. I would much prefer to keep this sort of toxic behavior off the ML. People can link to whatever helpful docs / blogs they choose. On Fri, Sep 9, 2016 at 1:12 PM Benedict Elliott Smith wrote: > Come on. This kind of inconsistent 'policing'

Re: Partition size

2016-09-09 Thread Benedict Elliott Smith
Come on. This kind of inconsistent 'policing' is not helpful. By all means, push the *committers* to improve the project docs as is happening, and to promote the internal resources over external ones. But Mark has absolutely no formal connection with the project, and his contributions have only

Re: Partition size

2016-09-09 Thread Jeff Jirsa
On 9/9/16, 12:14 PM, "Mark Thomas" wrote: > If you are going to point to docs, please >point to the official Apache docs unless there is a very good reason not to. > (And if the good reason is that there’s a deficiency in the apache Cassandra docs, please make it known on

Re: Partition size

2016-09-09 Thread Jeff Jirsa
On 9/9/16, 8:47 AM, "Rakesh Kumar" wrote: >> If your partition sizes are over 100MB iirc then you'll normally see >> warnings in your system.log, this will outline the partition key, at least >> in Cassandra 2.0 and 2.1 as I recall. > >Has it improved in C* 3.x.

Re: Partition size

2016-09-09 Thread Mark Thomas
On 09/09/2016 16:46, Mark Curtis wrote: > If your partition sizes are over 100MB iirc then you'll normally see > warnings in your system.log, this will outline the partition key, at > least in Cassandra 2.0 and 2.1 as I recall. > > Your best friend here is nodetool cfstats which shows you the >

Re: Partition size

2016-09-09 Thread Mark Curtis
On 9 September 2016 at 16:47, Rakesh Kumar wrote: > On Fri, Sep 9, 2016 at 11:46 AM, Mark Curtis > wrote: > > If your partition sizes are over 100MB iirc then you'll normally see > > warnings in your system.log, this will outline the

Re: Partition size

2016-09-09 Thread Rakesh Kumar
On Fri, Sep 9, 2016 at 11:46 AM, Mark Curtis wrote: > If your partition sizes are over 100MB iirc then you'll normally see > warnings in your system.log, this will outline the partition key, at least > in Cassandra 2.0 and 2.1 as I recall. Has it improved in C* 3.x.

Re: Partition size

2016-09-09 Thread Mark Curtis
If your partition sizes are over 100MB iirc then you'll normally see warnings in your system.log, this will outline the partition key, at least in Cassandra 2.0 and 2.1 as I recall. Your best friend here is nodetool cfstats which shows you the min/mean/max partition sizes for your table. It's

Duplicate fields in cassandra type

2016-09-09 Thread Олег Краюшкин
Hi Everyone, have a nice day and let me ask for your help. I'm using Cassandra 2.2.7. Since yesterday I'm getting the exception while connecting to the cluster via java driver (I'm using v3.0.3 ): [main] ERROR c.datastax.driver.core.SchemaParser - Error parsing schema from Cassandra system

Re: Isolation in case of Single Partition Writes and Batching with LWT

2016-09-09 Thread Benedict Elliott Smith
Yes, each partition modified by a batch has its modifications applied altogether, atomically (at the node level). On Friday, 9 September 2016, Bhuvan Rawal wrote: > As per this > doc > conditional batches

Re: Isolation in case of Single Partition Writes and Batching with LWT

2016-09-09 Thread Bhuvan Rawal
As per this doc conditional batches can contain queries only belonging to that partition. On trying it in 3.6 I got this exception as expected: InvalidRequest: Error from server: code=2200 [Invalid query] message="Batch with