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

Sylvain Lebresne commented on CASSANDRA-3761:
---------------------------------------------

@Thorsten:

bq. I assume I can do a column slice using something like

You assume well.

bq. I'm finding it very useful to abuse the wide-row column names a little bit 
to be able to group rows

I note your objection and use case. But to be clear, I only meant that the 
current patch don't support secondary indexes on wide rows, not that CQL 3 
wouldn't ultimately support them. I just meant that I'd prefer pushing support 
to a following ticket.
                
> CQL 3.0
> -------
>
>                 Key: CASSANDRA-3761
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3761
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>              Labels: cql
>             Fix For: 1.1
>
>         Attachments: 0001-CQL-3.0-v2.patch, 0001-CQL-3.0.patch, 
> 0002-Add-support-for-switching-the-CQL-version-v2.patch, 
> 0002-Add-support-for-switching-the-CQL-version.patch, 
> 0003-Makes-batches-atomic-v2.patch, 0003-Makes-batches-atomic.patch, 
> 0004-Thrift-gen-files-v2.patch, 0004-Thrift-gen-files.patch, cql_tests.py, 
> create_cf_syntaxes.txt
>
>
> This ticket is a reformulation/generalization of CASSANDRA-2474. The core 
> change of CQL 3.0 is to introduce the new syntaxes that were discussed in 
> CASSANDRA-2474 that allow to:
> # Provide a better/more native support for wide rows, using the idea of 
> transposed vie.
> # The generalization to composite columns.
> The attached text file create_cf_syntaxes.txt recall the new syntaxes 
> introduced.
> The changes proposed above allow (and strongly suggest in some cases) a 
> number of other changes to the language that this ticket proposes to 
> explore/implement (more details coming in the comments).

--
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