Ok, here are the common Cassandra misconceptions, and their sources,
gleaned from experience and talking to various people.
Not listed in any particular order.
1. A key is global, and data in different column families must be related.
- BigTable paper
- key precedence in Thrift API
2. Table
+1 from me.
On Aug 18, 2009, at 2:12 AM, ant elder wrote:
On Mon, Aug 17, 2009 at 4:55 PM, Eric Evanseev...@rackspace.com
wrote:
On Mon, 2009-08-17 at 13:00 +0100, sebb wrote:
Given whats being said in the Thrift release
legal issues thread i think it should be ok to have the 3rd party
I find the diagrams of Evan and folks
(http://blog.evanweaver.com/files/cassandra/twitter.jpg) much easier
to grok than any particular naming scheme. Annotating that diagram
with specific implementations or constraints, like your wiki page, is
a great addition.
.. Adam
On Mon, Aug 17, 2009 at
I've been thinking about this for a number of days, and again, while I am not a
developer I thought I might toss in a proposal if that's okay.
Since putting together a schema diagram and having a number of people review
it, I think a change is warranted. Too many people are coming from the RDBMS
