Storage Classes
Hi, Which classes in Cassandra are used to store data? Where can I find info on how Cassandra persists data? Is there a way to periodically take a snapshot of the persisted data without using the thrift client API? Does Cassandra persist data in a file on in memory? thanks in advance, BoriS
Re: Web console application
Hi Suguru, Congratulations for your web console, it's definitively the best graphic Cassandra console I've found so far. The problem is that we are using last Cassandra version, 0.6.3, and the console is not showing the data, even it's detecting the keyspaces. Is there any way we could have it working? Thank you!
Re: Storage Classes
This should be on the user list. Most of what you ask can easily be found on the Cassandra wiki with a cursory search. On Jul 22, 2010 4:31 AM, Boris Spasojevic boris.spasoje...@epfl.ch wrote: Hi, Which classes in Cassandra are used to store data? Where can I find info on how Cassandra persists data? Is there a way to periodically take a snapshot of the persisted data without using the thrift client API? Does Cassandra persist data in a file on in memory? thanks in advance, BoriS
network compatibility from 0.6 to 0.7
How useful is this to insist on, given that 0.7 thrift api is fairly incompatible with 0.6's? (timestamp - Clock change being the biggest problem there) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
Re: network compatibility from 0.6 to 0.7
As long as network compatibility is in place, it is possible to incrementally upgrade a cluster by restricting thrift clients to only talk to the 0.6 nodes until half the cluster is upgraded and then modify them to talk to the 0.7 nodes. If networking compatibility breaks, there is no way to avoid downtime or even test 0.7 under production load. On Jul 22, 2010 9:50 AM, Jonathan Ellis jbel...@gmail.com wrote: How useful is this to insist on, given that 0.7 thrift api is fairly incompatible with 0.6's? (timestamp - Clock change being the biggest problem there) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
RE: network compatibility from 0.6 to 0.7
So I think we should probably try to preserve compatibility in 0.7. We could probably limit the scope of our network compatibility to steady-state messages, aka, nothing having to do with bootstrap, repair, etc. -Original Message- From: Stu Hood stu.h...@rackspace.com Sent: Thursday, July 22, 2010 12:35pm To: dev@cassandra.apache.org Subject: RE: network compatibility from 0.6 to 0.7 I feel like the next time we break network compatibility should be the last time, aka, the release when we introduce a backwards compatible RPC layer (Avro?), and implement support for dropping messages that a node can't handle. So I think we should probably try to preserve compatibility in 0.7. -Original Message- From: Jonathan Ellis jbel...@gmail.com Sent: Thursday, July 22, 2010 11:49am To: cassandra-...@incubator.apache.org Subject: network compatibility from 0.6 to 0.7 How useful is this to insist on, given that 0.7 thrift api is fairly incompatible with 0.6's? (timestamp - Clock change being the biggest problem there) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
Re: network compatibility from 0.6 to 0.7
What would be the pros of breaking it for 0.7 now ? I suppose you have something specific in mind that would break compatibility ? On Thu, Jul 22, 2010 at 8:19 PM, Gary Dusbabek gdusba...@gmail.com wrote: I think this depends on how much value users place in rolling upgrades (it's going to vary). My opinion is that we should be allowed to break it between major versions if required. Gary. On Thu, Jul 22, 2010 at 11:49, Jonathan Ellis jbel...@gmail.com wrote: How useful is this to insist on, given that 0.7 thrift api is fairly incompatible with 0.6's? (timestamp - Clock change being the biggest problem there) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
Re: 0.6.4
+1 On Wed, Jul 21, 2010 at 17:59, Eric Evans eev...@rackspace.com wrote: It's been the better part of a month since 0.6.3, so it's probably a good time to start thinking about an 0.6.4. Barring objections, I'd like to tag next Tuesday July 27, and move anything not completed by then to 0.6.5. As usual, if you have something you think should make it in, but need more time, then let's discuss. -- Eric Evans eev...@rackspace.com
