The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.1.7.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
http://cassand
>
> To my understanding client will not be notified because this read step is
> asynchronously.
Yes, though for the record it's actually synchronous if you use anything
else than CL.ONE.
> Also the other replica cannot be updated properly (replicate-on-write
> stage is backing up).
> Question i
One thing to consider is hector-client master supports bigdecimal,
reversed type and other CQL3 features.
I don't use astyanax, so I didn't bother contributing the changes to them.
If you don't use CQL and don't really care, they're functionally equal
in my bias opinion. If you do use CQL2 or CQL
Does anyone have any comments/suggestions for me regarding this? Thanks
I am trying to understand some strange behavior of cassandra row cache. We
> have a 6-node Cassandra cluster in a single data center on 2 racks, and the
> neighboring nodes on the ring are from alternative racks. Each node
Hi:
Are there any known issues with initial_token collision when adding nodes to a
cluster in a VM environment?
I'm working on a 4 node cluster set up on a VM. We're running into issues when
we attempt to add nodes to the cluster.
In the cassandra.yaml file, initial_token is left blank.
Since
The nodetool snapshot command has keyspace and column family options (from
nodetool --help):
snapshot [keyspaces...] -cf [columnfamilyName] -t [snapshotName] - Take a
snapshot of the optionally specified column family of the specified
keyspaces using optional name snapshotName
On Wed, Nov 28, 20
