+1. There is some disagreement on whether or not the API should return empty columns or skip rows when no data is found. In all of our use cases, we would prefer skipped rows. And based on how frequently new cassandra users appear to be confused about the current behaviour, this might be a more common use case than the need for empty cols. Perhaps this could be added as an option on SlicePredicate ? (e.g. skipEmpty=true).
On Fri, May 7, 2010 at 12:59 AM, Mike Malone <m...@simplegeo.com> wrote: > On Thu, May 6, 2010 at 3:27 PM, Ian Kallen <spidaman.l...@gmail.com> wrote: >> >> Cool, is this a patch you've applied on the server side? Are you running >> 0.6.x? I'm wondering if this kind of thing can make it into future versions >> of Cassandra. > > Yea, server side. It's basically doing the same thing clients typically want > to do (again, at least for our use cases) but doing it closer to the data. > Our patch is kind of janky though. I can probably get some version of it > pushed back upstream - or at least on github or something - if there's any > interest. > Mike
