Does anyone have a simple app schema they can share?
I can't share the one for our main app. But we do need an example
here. A real one would be nice if we can find one.
I checked App Engine. They don't have a whole lot of examples either.
They do have a really simple one:
http://code.google.
Great!
Sure, contact me off-list.
-Chris
On May 18, 2009, at 6:25 PM, Jonathan ellis wrote:
Different apps will have different performance characteristics (and
different key domains, which can also be important). So there are
operational reasons to prefer cluster-per-app.
That said, mul
Different apps will have different performance characteristics (and
different key domains, which can also be important). So there are
operational reasons to prefer cluster-per-app.
That said, multi table support is high on my priority list. The
changes required are straightforward so I'd
Has anyone here needed multi-table support yet in Cassandra? Anyone
willing to share use cases where you felt maybe you didn't need multi-
table support? Seems just a bit odd it isn't there yet :)
---
Chris Goffinet
goffi...@digg.com
That's the price you pay for (a) eventual consistency in general and
(b) doing read repair in the background specifically. Cassandra also
has functionality (called "strong read") to do a quorum read in the
foreground and repair if necessary but that is not exposed in Thrift
yet -- but even with th
Scenario: if i setup a 2 node cluster, with replicationfactor of 2.
Inserted a new key (1) into a table. Its replicated to both nodes. I
shutdown node (2), delete all data, then bring it back up. I noticed
that if i make a request to that node the first time for that key, it
will return bac
