[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3647:
--------------------------------------
Summary: Support arbitrarily nested sets and maps in CQL (was: Support
arbitrarily nested "documents" in CQL)
Editing title to reflect reduced scope.
Not sure that we can really support lists meaningfully. [Sorted] sets is a
much clearer mapping to C*, i.e., people don't expect to be able to write
"set[3] = foo" and have some magic index -> column name mapping happen.
Also, another source of prior art is
http://www.postgresql.org/docs/9.1/static/hstore.html. I like the use of the
|| operator for concatenation, but I'm not sure why they invented this whacky
one-off syntax for maps instead of using json. Is there a good reason I don't
see why json conflicts with SQL? Or did the person who wrote it just like the
old Ruby hash syntax (which, I note that Ruby deprecated because it's so
cumbersome)?
> Support arbitrarily nested sets and maps in CQL
> -----------------------------------------------
>
> Key: CASSANDRA-3647
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3647
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
