Cassandra 0.8.1 has been out for a few weeks now and we have had a number of
fixes since then. It feels like a good time to relase 0.8.2. But there is also
the fact that 0.8.1 suffers from the same regression than 0.7.7, that is:
https://issues.apache.org/jira/browse/CASSANDRA-2928
For both those
Including my own +1, I count 3 binding +1s and no -1s. The vote passes.
I'll get the artifacts published shortly.
On Thu, Jul 21, 2011 at 9:16 PM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Thu, Jul 21, 2011 at 10:11 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
Cassandra 0.7.7 has
Thanks Ryan.
We talked about this idea in the dev channel the other day and Brandon and Ed
thought it sounded good too. I've created a short-term jmx related ticket but
seems like longer term we could have a default and max defined in the yaml, but
allow the rpc timeout to be set per call as
I just ran into an issue where CQL queries that were written at the time
of 0.8.0 no longer work against 0.8.1. This was caused by r1130200
(CASSANDRA-1709) which introduced ALTER support. The queries in
question made use of unquoted terms for one of the newly added keywords
(type in this case
