Thanks Jonathan!
So let's see if I got this right.
Just like an overview data being stored like HashMap<row, SortedMap<name, val>>
and in case of a superColumnFamily HashMap<row, SortedMap<super, SortedMap<name, val>>>?

Does that mean that when using columns as indexes we need to deserialize
So when asking for a column in  a row, the whole row structure first need to be deserialized
and then we can get the columns we are looking for?

And in that case when using rows as indexes instead of columns we only need to read

On Mon, Mar 1, 2010 at 11:24 AM, Jonathan Ellis <> wrote:
On Mon, Mar 1, 2010 at 12:50 PM, Erik Holstad <> wrote:
> I've been looking at the source, but not quite find the things I'm looking
> for, so I have a few
> questions.
> Are columns for a row stored in a serialized data structure on disk or
> stored individually and
> put into a data structure when the call is being made?

The former, but only for top-level columns -- subcolumns are all read
at once for slices against supercolumns.

Regards Erik