This really depends on the operations you want to optimize for. What's
important to you? Aggregate queries? Finding children/siblings/ancestors?
Reorganizing the tree/hierarchy?
For Cassandra, you really need to spend time thinking about how you'll be
accessing things and design for that.
If
Ok, so 0.6's https://issues.apache.org/jira/browse/CASSANDRA-745 permits
someone using RandomPartitioner to pass start= and finish= to get all
of the rows in their cluster, although in an extremely inefficient way.
We are in a situation like Pierre's, where we need to know what's currently
in the
+1
On Mon, Jan 25, 2010 at 1:11 PM, Eric Evans eev...@rackspace.com wrote:
There was some additional discussion[1] concerning Cassandra's
graduation on the incubator list, and as a result we've altered the
initial resolution to expand the size of the PMC by three to include our
active
