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

Jawahar Prasad JP commented on CASSANDRA-3761:
----------------------------------------------

Ok. I got it. Another question:

1. For example: I have columnfamily to store the broken links :

        broken_link_id uuid PRIMARY KEY,
        site_id uuid,
        site_url text,
        page_url text,
        broken_link text,
        anchor_text text,
        tstamp timestamp

I want something like this:
site_id, site_url, page_url, {broken_link_id,broken_link,anchor_text,tstamp}

I came up with this WRONG version:
CREATE COLUMNFAMILY broken_links (
        broken_link_id uuid,    
        site_id uuid,
        site_url text,
        page_url text,
        broken_link text,
        anchor_text text,
        tstamp timestamp,
        PRIMARY KEY(site_id, site_url, page_url)
);
Can you let me know how do I write this correctly please ? Or is there any doc 
to take a look at this(for CQL) ?

2. How do you know what columns to be considered as composite based on PRIMARY 
KEY?
                
> 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

        

Reply via email to