[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250501#comment-13250501
]
Sylvain Lebresne commented on CASSANDRA-3647:
---------------------------------------------
bq. Note that we never actually need to compare the different types, since
sub-components of types X and Y will always have a different parent component.
We just need to allow them
True, but I guess that was the UnionType part of it, whose goal is to allow
that. For MapType and ListType, I agree they don't add much in term of
comparison, but I still think it *may* be a good idea to declare them, even if
they are just alias (like ListType would be an alias for UUIDType), just so
that map-reduce and other external tool know that we meant a list, not a uuid,
by just looking at the comparator (could be handy for debugging too). But I'm
probably getting carried away, those are implementation details and may or may
not be feasible/desireable. My point was that as far as supporting internally
whatever encoding we chose, adding a UnionType would be an option (one I like
more than a json encoding personally), and that's fairly trivial to write.
At the more general level, I'm wondering how to return that to the client, in
the ResultSet. It's unclear to me how to support even just map and list in
there in a useful way. Of course there is the approach of returning a json
string, which I'll admit I'm not a super fan because 1) it's only convenient
for those that wants json and 2) it feels at odd with our current API that is
not json at all.
> Support arbitrarily nested "documents" 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
