cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3647) Support arbitrarily nested "documents" in CQL
Date Tue, 10 Apr 2012 13:43:21 GMT


Jonathan Ellis commented on CASSANDRA-3647:

Well, the ResultSet isn't written in stone itself; it's always been kind of a placeholder
pending CASSANDRA-2478.  Our custom transport could represent the entire resultset in json
(or Smile) if we want, which is the approach unql appears to take:

For the existing Thrift transport though I'm not super concerned about it, as long as we come
up with something halfway reasonable (which json-encoding qualifies as), I'm okay with it.

Alternatively, we could use a more compact, custom format leveraging the fact that we know
the types involved (and thus don't need to implicitly encode those in an inefficient representation),
e.g. for Map number of entries followed by key/value pairs in native binary format.
> Support arbitrarily nested "documents" in CQL
> ---------------------------------------------
>                 Key: CASSANDRA-3647
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>              Labels: cql
> Composite columns introduce the ability to have arbitrarily nested data in a Cassandra
row.  We should expose this through CQL.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message