[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095749#comment-13095749
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. I think we better have them so users won't get confused
We already have the transposition as a visual "hint" as to what is going on. I
don't think it's difficult to say that "you need to use componentX when using
transposition," and :colon tokens are usually used to represent bind variables
in SQL drivers.
bq. Maybe it is better if we will support (..,..,..) notation for composite
columns
What does this buy us?
bq. even in your example when we will try to add a new <location> field it will
be very hard to guess how column name was looking previously
Sorry, I don't follow.
Note: Eric Evans on IRC suggested that we simplify this by only supporting
"normal" and composite columns, leaving out supercolumns until a future release
where supercolumns are reimplemented with composites under the hood. That
seems reasonable to me, and should simplify implementation.
> CQL support for compound columns
> --------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> Project: Cassandra
> Issue Type: Sub-task
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Pavel Yaskevich
> Labels: cql
> Fix For: 1.0
>
> Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> For the most part, this boils down to supporting the specification of
> compound column names (the CQL syntax is colon-delimted terms), and then
> teaching the decoders (drivers) to create structures from the results.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
