cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3761) CQL 3.0
Date Mon, 23 Jan 2012 14:22:40 GMT

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

Jonathan Ellis commented on CASSANDRA-3761:
-------------------------------------------

The PK(X, Y) syntax tells Cassandra to use composite columns internally for that row.  This
has two effects.  First, as Sylvain mentioned above, if you just have the userid as PK then
(just as in SQL) you may only have one row with that key, which is not what you want here.
 Second, it gives you some sorting guarantees for range queries like your posted_at > Z
example.  See http://www.datastax.com/dev/blog/introduction-to-composite-columns-part-1 for
more background on composites.

That said, this really isn't the right place to discuss the basics of querying composites.
 Let's keep that on the user mailing list, please.
                
> 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
>              Labels: cql
>             Fix For: 1.1
>
>         Attachments: 0001-CQL-3.0.patch, 0002-Add-support-for-switching-the-CQL-version.patch,
0003-Makes-batches-atomic.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

        

Mime
View raw message