On Mon, Aug 6, 2012 at 4:49 AM, Sylvain Lebresne <sylv...@datastax.com> wrote: >> 2. JSON does not have a rich enough vocabulary to imply all of the CQL types >> without this additional information. > > JSON really just was a kind of first try, because it made it easy to > test the collection code. CASSANDRA-4453 brings a more suitable > encoding (I note that the currently patch attached stick to json for > thrift, but as I said in the comments, it's a one line change to > modify that).
That said, it should still be possible to decode correctly by using the type information from CqlMetadata.value_types. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
