In the case without CQL3, where I would use composite columns, I see how
this sort of lines up with what CQL3 is doing.
I don't have the ability to use CQL3 as I am using pycassa for my client,
so that leaves me with CompositeColumns
Under composite columns, I would have 1 row, which would be
I have heard it best to try and avoid the use of super columns for now.
Yup.
Your model makes sense. If you are creating the CF using the cassandra-cli you
will probably want to reverse order the column names see
http://thelastpickle.com/2011/10/03/Reverse-Comparators/
If you want to use
My use case is capturing some information about Instagram photos from the
API. I have 2 use cases. One, I need to capture all of the media data for
an account and two I need to be able to privately annotate that data. There
is some nuance in this, multiple http queries for example, but ignoring
