[ https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095962#comment-13095962 ]
Pavel Yaskevich commented on CASSANDRA-2474: -------------------------------------------- bq. I think the goal should be to make it look more like SQL when that is reasonable. I hope that the main goal here is to give end-user clean syntax instead of trying to be as SQL as possible in all the cases. bq. That would imply a "rename column" operation. I don't want to go there. I guess I described it wrong - we can insert new column with name "2e1c3308,cscotta,<location>" and still use "1/0/-1" as <'end-of-component' byte> for querying. Is there any reason why we should delete "2e1c3308,cscotta" I'm missing? > 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