> there a situation in which that behavior would be useful?
guessing, makes life easier to client implementations and is consistent in the
sense that when doing a slice by name the server is the entity that decides
which columns are in the result set.
I took a look at the performance of variou
Hi Aaron,
Thanks for the answer. That makes sense and I can see it as a formal
reason for returning empty columns, but as a practical matter, is
there a situation in which that behavior would be useful?
Unfortunately a column slice won't do the trick -- the columns we're
looking for at any given
If you specify the columns by name in the select clause the query returns them
because they should be projected in the result set.
Can you use a column slice instead ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 17/08/2012, at 11:09 A
Hello all,
I've noticed that when performing a SELECT statement with a list of
columns specified, Cassandra returns all columns in the resulting
row(s) even if they have no value. This creates an apparently
considerable amount of transport and deserialization overhead,
particularly in one use case
