tors who didn't
have commit access.
The three major contributors all agreed to this move.
That's all.
Gary Dusbabek
Node fan boy, CQL wrangler.
What used to be at https://github.com/racker/node-cassandra-client
is now found at http://code.google.com/a/apache-extras.org/p/cassandra-node
That is all.
Gary.
I've seen one or two instances of bit-rot in the avro CassandraServer,
and I suspect there are probably others. It doesn't get first-class
testing status, so I suspect it will be buggy unless it gets more
usage by others.
One other aspect is there is a fair amount of code baggage that needs
to be
>
> I still think the query language is a good idea but I have one
> negative point about it.
>
> One of the selling point about a simple data model and access language
> was that there were never issues where a query planner "refused" to do
> the query the "optimal way" the user desired. For examp
Client devs:
Because of some race conditions that will be difficult to fix without
tearing up a lot of things, I'll be removing the
system_rename_column_family and system_rename_keyspace methods from
the client API sometime today. They'll make their first disappearance
in what will likely be 0.7-
Hi everybody. This is a heads-up for 3rd-party client developers.
I should have sent this out when the feature first went in, but it
wasn't on my mind. My apologies.
Shortly after CASSANDRA-44 (create KS/CF on a live cluster) was
committed, we had a request to provide a way to update those sett
check_schema_agreement() can be used for this right now. The downside
is that it contacts every node in the cluster. They map key in the
results (hopefully there should be only one key) is the current schema
version uuid that has been stringified.
Gary.
On Wed, Sep 1, 2010 at 04:12, Dan Washus
