Thanks Nate. I will take a look at extending thrift, seems like this could be useful for some folks.
On Friday, December 20, 2013 at 12:29 PM, Nate McCall wrote: > > > > My questions – > > > > 1) Is this supported in the Thrift interface or CQL? > > Not directly, no. > > > 2) If not, is there clever data modeling or indexing that could accomplish > > this use case? 1 single-row round-trip to get these columns? > > > > > If this is a query done frequently you could prefix both columns with a > static value, eg. ["foo:username....", foo:city...", "bar:other_column:..."] > so in this specific case you look for 'foo:*' > > > 3) Is there plans to support this in the future? Generally, what is the > > future of composite columns in a CQL world? > > > > You can always extend cassandra.thrift and add a custom method (not as hard > as it sounds - Thrift is designed for this). Side note: DataStax Enterprise > works this way for reading the CassandraFileSystem blocks. An early > prototype: > https://github.com/riptano/brisk/blob/master/interface/brisk.thrift#L68-L80 > > > > -- > ----------------- > Nate McCall > Austin, TX > @zznate > > Co-Founder & Sr. Technical Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com
