A few quick comments:
* its not clear what column family the super column you're using is in.
* it might be useful to include the timestamps in the columns (since
they're user-supplied)
* given that the colon-delimited api has been removed, it might be
easier to explain the data model without
Thanks for taking a stab at this, Mark.
I'm not a fan of teaching this by showing CF-spanning rows. (The
bigtable paper does this IIRC but it's wrong. :)
You can have data in different CFs with the same key, yes, but all
that means is they will be stored on the same nodes. Each CF is
stored
FWIW: I find that the only sane way to visually represent a data model
is to use a JSON-ish notation.
Picture type visualizations confuse me even more.
I don't mean to be a downer but me and a lot of my peers found all the
picture type visual aides even more confusing
-arin
aka: phatduckk
On
On Thu, Aug 13, 2009 at 5:12 PM, Arin Sarkissiana...@rspot.net wrote:
FWIW: I find that the only sane way to visually represent a data model
is to use a JSON-ish notation.
Picture type visualizations confuse me even more.
I don't mean to be a downer but me and a lot of my peers found all the
