I agree that it is worth adding a support for counter as supercolumns in 1546 and that's fairly trivial, so I will add that as soon as possible (but please understand that I'm working on this for a good part during my free time).
As for supercolumns of counters, there is what Jonathan proposes, but I'll add that encoding a supercolumns CF to a standard column CF is almost always a fairly trivial encoding. Worst case scenario it requires you to roll up your own comparator and it's slightly less convenient for client code. On Tue, Sep 28, 2010 at 10:38 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Tue, Sep 28, 2010 at 3:35 PM, Ryan King <r...@twitter.com> wrote: >> On Tue, Sep 28, 2010 at 12:48 PM, Jonathan Ellis <jbel...@gmail.com> wrote: >>> On Tue, Sep 28, 2010 at 2:25 PM, Ryan King <r...@twitter.com> wrote: >>>> Sorry, been catching up on this. >>>> >>>> From Twitter's perspective, 1546 is probably insufficient because it >>>> doesn't allow one to do time-series data without supercolumns (which >>>> might work ok, but require a good deal of work). Additionally, one of >>>> our deployed systems already does supercolumns of counters, which is >>>> not feasible in this design at all. >>> >>> True, although wouldn't rows-of-counters give you basically the same >>> thing if 1546 kept its counters as subcolumns of a supercolumn? >> >> That would solve the first part (single-dimension time-series), but we >> also do supercolumns of counters, which 1546 doesn't appear to be able >> to address. > > Right, I'm saying that "rows of counters + get_range_slices" looks a > lot like "supercolumns of counters + get_slice" to me. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com >
