> but from what I understand, there is no support for this in CQL3?
Whether or not there is "support" probably depends on your definition of
"support". It is "possible" to do in CQL3 if that is your question.
What can be said however is that CQL3 does not consider that every type
should
have an e
We have wide rows which are composite of integer.byte array where some of our
columns are {empty}.byte array (ie. The first part of the composite key is
empty as in 0 length string or 0 length integer(ie. NOT 0, but basically null)
This has worked great when we look up all the entries with a emp
