Implementing a driver for cassandra native protocol v2

2013-10-26 Thread Mathieu D'Amours
Hello, I'm currently implementing an Erlang driver for Cassandra's binary protocol v2. Most of it is straightforward, but I came across this part in [4.1.4. QUERY]: > is a [byte] whose bits define the options for this query and > in particular influence what the remainder of the message con

Re: Implementing a driver for cassandra native protocol v2

2013-10-28 Thread Mathieu D'Amours
Great, then I guess the same issue applies for [4.2.5.2. Rows]. Le Oct 28, 2013 à 10:17 AM, Sylvain Lebresne a écrit : > On Sat, Oct 26, 2013 at 8:07 PM, Mathieu D'Amours wrote: > >> Hello, >> >> I'm currently implementing an Erlang driver for Cassandra'

Authentication in cassandra binary protocol v2

2013-10-28 Thread Mathieu D'Amours
Hello, I stumbled upon this description in the binary protocol specs [4.2.7. AUTH_CHALLENGE]: > The body of this message is a single [bytes] token. The details of what this > token contains (and when it can be null/empty, if ever) depends on the actual > authenticator used. I looked in C* buil

Re: Authentication in cassandra binary protocol v2

2013-10-28 Thread Mathieu D'Amours
t that specific authenticator expect (basically the username and > password as UTF8). > > -- > Sylvain > > > On Mon, Oct 28, 2013 at 7:15 PM, Mathieu D'Amours wrote: > >> Hello, >> >> I stumbled upon this description in the binary protocol specs [4.2

Lifecycle of paged queries

2013-11-18 Thread Mathieu D'Amours
Hello everyone, I'd like to know how long a paged query state lives in C* before being gc'd if the client never comes and query the rest. - Matt

Data serialization from clients

2013-11-19 Thread Mathieu D'Amours
Hello everyone, I just want to make sure, the set of bounds values provided along QUERY or EXECUTE requests coming from clients should be encoded in accordance with serializers found in org.apache.cassandra.serializers.* right? - Matt

Named bind variables and one-off queries

2013-11-20 Thread Mathieu D'Amours
Hello again, Since C* expect a list of values for bind variables in queries, in non-prepared queries the driver has no direct information about the expected order of named variables. Is there a way to reliably predict the order of variable values C* will expect?

Re: Named bind variables and one-off queries

2013-11-20 Thread Mathieu D'Amours
gt; On Wed, Nov 20, 2013 at 10:13 AM, Mathieu D'Amours wrote: > >> >> Since C* expect a list of values for bind variables in queries, in >> non-prepared queries the driver has no direct information about the >> expected order of named variables. Is there a way t

Re: Named bind variables and one-off queries

2013-11-20 Thread Mathieu D'Amours
OK, that answers my question, thank you! - Mathieu Le Nov 20, 2013 à 11:31 AM, Sylvain Lebresne a écrit : >> Since C* expect a list of values for bind variables in queries, in >> non-prepared queries the driver has no direct information about the >> expected order of named variables. Is there a

Cassandra documentation

2014-02-17 Thread Mathieu D'Amours
Hello, In cassandra's documentation page http://www.datastax.com/documentation/cassandra/2.0/cassandra/configuration/configCassandra_yaml_r.html, in the section about start_native_transport, the following is written: > "Currently, only the Thrift server is started by default because the native