On 2010-08-02, at 02:22 , Jonathan Ellis wrote:
As far as thrift mode goes, you really have to rely on the user to
specify the correct version (since connecting with framed mode, to an
unframed server, can crash it).
In 0.7 framed mode will be the default and I am strongly in favor of
removing
As far as thrift mode goes, you really have to rely on the user to
specify the correct version (since connecting with framed mode, to an
unframed server, can crash it).
In 0.7 framed mode will be the default and I am strongly in favor of
removing the unframed option entirely in 0.8.
On Sun, Aug 1
On 2010-08-01, at 19:31 , Jonathan Ellis wrote:
use the describe_version thrift api call
in principle, obvious.
on the other hand, how does one know whether or not to send the frame
header?
is there a standard probe one can send?
is there a standard .7 server behaviour if no frame was se
use the describe_version thrift api call
On Sun, Aug 1, 2010 at 2:00 AM, james anderson wrote:
> good morning;
>
> is there somewhere a description of - or code which does, protocol version
> negotiation? particularly client code, across the 0.6/0.7 transition.
>
> all pointers would be welcome.
Glad to see this, and I hope you'll be able to take advantage of the
secondary index features coming in 0.7.
Supporting different lower-level "drivers" seems like wasted effort to me, fwiw.
On Sat, Jul 31, 2010 at 8:54 AM, Sanjay Sharma
wrote:
> Hi All,
>
> We are happy to announce and share a n
> storms and very slow responses. Also, I'd like to be able to load more data
> to the cluster and I'm hitting the memory wall, which I didn't expect.
> In the cassandra.in.sh you'd notice that I do provide Xmx=12G but given that
> there's so little data I wouldn't expect the process to be using al
Hi all
Nowadays I'm using Cassandra DB under high read/write loads.
I have two questions:
First, Cassandra suddenly dies during compaction. Java core dump says that
the last thread run was "COMPACTION-POOL:1".
I suspect that my business logic could lead size of columns in a column
family per a
good morning;
is there somewhere a description of - or code which does, protocol
version negotiation? particularly client code, across the 0.6/0.7
transition.
all pointers would be welcome.
