Basically add a column to ypur primary key called name which is a string
and a column named value ttyped bytes. Or a map of byte bye named extra, or
just use compact storage lile i do.
On Wednesday, July 31, 2013, Jon Ribbens <jon-cassan...@unequivocal.co.uk>
wrote:
> I thought that part of the point of Cassandra was that, unlike a
> standard relational database, each row does not have to have the same
> set of columns. I don't understand how this squares with CQL. If I want
> to have a table ("column family"?) with a few fixed columns that are
> relevant to every row, I can create that with CQL's CREATE TABLE, but
> if I then want to set extra columns with arbitrary names on various
> rows, how do I tell CQL what type those columns are? Or is this
> feature of Cassandra now deprecated?
>
