[ 
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173278#comment-13173278
 ] 

Sylvain Lebresne commented on CASSANDRA-2474:
---------------------------------------------

bq. This is adapting exactly to the relational philosophy that SQL is about 
sets of records and predicates that deal with them

I suppose this sums up my objections and why I can't get myself to be fully 
convinced by those propositions. I had though at first that the goal of CQL was 
to use a query language because this was making it much more easy to make it 
evolve without breaking clients (and why not a syntax close to SQL as long as 
it doesn't constrain us in any way -- though that was fishy from the start). 
But I didn't though the goal was to 'adapt to the relational philosophy'. I 
don't like that idea (for a number of reasons but it's not the place for 
those), I think we are impoverishing Cassandra going this road, and truth is, 
it's not the first time I've had a bad feeling about this.

But it's very possible that fitting to the relational philosophy is good for 
adoption, and that it's the best solution for CQL at this point (I should 
probably have cared for CQL and object to it sooner anyway), so ranting being 
made, I'll shut up and try to first embrace the relational philosophy to 
hopefully make more constructive criticisms :)
                
> CQL support for compound columns
> --------------------------------
>
>                 Key: CASSANDRA-2474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Pavel Yaskevich
>              Labels: cql
>             Fix For: 1.1
>
>         Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG, 
> 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG, 
> raw_composite.txt, 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.
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

        

Reply via email to