Ok, your results are pretty impressive, I'm giving it a try. I've made
some initial attempts to use Astyanax 1.56.37, but have some troubles:
- it's not compatible with 1.2.8 client-side ( NoSuchMethodError's on
org.apache.cassandra.thrift.TBinaryProtocol, which changed it's
signature since
I'm running Cassandra 1.2.6 without compact storage on my tables. The trick is
making your Astyanax (I'm running 1.56.42) mutation work with the CQL table
definition (this is definitely a bit of a hack since most of the advice says
don't mix the CQL and Thrift APIs so it is your call on how far
On Thu, Sep 12, 2013 at 2:13 AM, Christopher Wirt wrote:
> I would like to switch to using LZ4 compression for my SStables. Would
> simply altering the table definition mean that all newly written tables are
> LZ4 and can live in harmony with the existing Snappy SStables?
>
Yes, per Aleksey in #c
On Thu, Sep 12, 2013 at 5:42 AM, Shahab Yunus wrote:
> I admit about missing details. Sorry for that. The thing is that I was
> looking for guidance at the high-level so we can then sort out myself what
> fits our requirements and use-cases (mainly because we are at the stage
> that they could be
Hi all!
According to the DataStax blog
(http://www.datastax.com/dev/blog/modern-hinted-handoff), once the dead node is
up again, all the nodes that have hints to the node start sending information.
However, it is written that they verify at every 10 minutes if there were timed
out hints.
Do t
Aaron, thanks for the super-rapid response. That clarifies a lot for me,
but I think I am still wondering about one point embedded below.
> From: aa...@thelastpickle.com
> Subject: Re: is the select result grouped by the value of the partition key?
> Date: T
I admit about missing details. Sorry for that. The thing is that I was
looking for guidance at the high-level so we can then sort out myself what
fits our requirements and use-cases (mainly because we are at the stage
that they could be molded according to hardware and software
limitations/features
I current use Snappy for my SSTable compression on Cassandra 1.2.8.
I would like to switch to using LZ4 compression for my SStables. Would
simply altering the table definition mean that all newly written tables are
LZ4 and can live in harmony with the existing Snappy SStables?
Then naturall