I'm currently in the process of porting my app from Thrift to CQL3 and it seems to me that the underlying storage layout hasn't really changed fundamentally. The difference appears to be that CQL3 offers a neater abstraction on top of the wide row format. For example, in CQL3, your query results are bound to a specific schema, so you get named columns back - previously you had to process the slices procedurally. The insert path appears to be tighter as well - you don't seem to get away with leaving out key attributes.
I'm sure somebody more knowledgeable can explain this better though. Cheers, Ben On Wed, Jan 9, 2013 at 4:51 PM, mrevilgnome <mrevilgn...@gmail.com> wrote: > We use the thrift bindings for our current production cluster, so I > haven't been tracking the developments regarding CQL3. I just discovered > when speaking to another potential DSE customer that wide rows, or rather > columns not defined in the metadata aren't supported in CQL 3. > > I'm curious to understand the reasoning behind this, whether this is an > intentional direction shift away from the big table paradigm, and what's > supposed to happen to those of us who have already bought into > C* specifically because of the wide row support. What is our upgrade path? >
