[ https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087831#comment-13087831 ]
Jonathan Ellis edited comment on CASSANDRA-2474 at 8/19/11 5:48 PM: -------------------------------------------------------------------- That would come from the schema, similar to how we have key_alias. (Implementation TBD, especially for "dynamic composite columns." For those we might just have to reserve component1, component2, etc. names) was (Author: jbellis): That would come from the schema, similar to how we have key_alias. (Implementation TBD, especially for "dynamic composite columns.") > 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 > Labels: cql > Fix For: 1.0 > > > 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