only real benefit
is optimised for CQL (which has limitations as you posted in your first
email).
On Tue, Dec 17, 2013 at 3:15 PM, Stuart Broad wrote:
> Based on an question I posted a while back I got the following answer (for
> something unrelated to this):
>
> When we speak of
tter cassandra user/developer.
>
>
> On Tue, Dec 17, 2013 at 9:08 AM, Stuart Broad wrote:
>
>> Hopefully this is a valid clarification, rather than a hijack of your
>> thread!
>>
>> How does the binary protocol fit into this? I have not used it but was
>>
Hopefully this is a valid clarification, rather than a hijack of your
thread!
How does the binary protocol fit into this? I have not used it but was
told you can implement CQL calls via thrift or via the binary protocol. Is
the binary protocol superior to thrift?
If you use the binary protocol
I'll not that even if you do want to use thrift, it's
> usually advised to use a high level client rather than raw thrift. Unless
> you have no choice or like suffering that is.
>
> --
> Sylvain
>
>
> On Tue, Apr 23, 2013 at 5:38 PM, Stuart Broad wrote:
>
>&
an optional property of the InvalidRequestException in
> future versions.
>
> Switching to the "binany protocol" is not a method in thrift, it means
> your not using thrift at all.
>
>
>
>
> On Tue, Apr 23, 2013 at 11:13 AM, Stuart Broad wrote:
>
>> Hi Edward,
>>
&g
>
> On Tue, Apr 23, 2013 at 10:29 AM, Stuart Broad wrote:
>
>> Hi all,
>>
>> I just realised that the binary protocol is the low-level thrift api that
>> I was originally using (Cassandra.Client>> get / insert ...). How can a
>> prepared statement be call
ou're
>> really considering preparing more than 10 statements, I'd suggest that
>> it might be worth benchmarking whether using prepared statements in your
>> case is really going to be worth the trouble. Just saying.
>>
>> --
>> Sylvain
>>
prepared statements in your
> case is really going to be worth the trouble. Just saying.
>
> --
> Sylvain
>
>
>
> On Tue, Apr 23, 2013 at 12:14 PM, Stuart Broad wrote:
>
>> Hi Sorin,
>>
>> The PreparedQueryNotFoundException is not thrown from
>> C
.but it least it works for now!
Cheers,
Stuart
On Sun, Apr 21, 2013 at 11:51 AM, Sorin Manolache wrote:
> On 2013-04-19 13:57, Stuart Broad wrote:
>
>> Hi,
>>
>> I am using Cassandra.Client
>> prepare_cql3_query/execute_**prepared_cql3_query to create and run some
>
(I
will do some investigation on Monday and post an update if I figure out the
exact messages).
Regards,
Stuart
On Fri, Apr 19, 2013 at 11:23 PM, Sorin Manolache wrote:
> On 2013-04-19 13:57, Stuart Broad wrote:
>
>> Hi,
>>
>> I am using Cassandra.Client
>&g
Hi,
I am using Cassandra.Client prepare_cql3_query/execute_prepared_cql3_query
to create and run some prepared statements. It is working well but I am
unclear as to how long the server side 'caches' the prepared statements.
Should a prepared statement be prepared for every new Cassandra.Client?
11 matches
Mail list logo
