You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/23 04:39:03 UTC

[jira] [Commented] (CASSANDRA-6076) implement HELP COMPOSITE_PRIMARY_KEYS

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

Jonathan Ellis commented on CASSANDRA-6076:
-------------------------------------------

+1, but can you fix composite -> compound wrt primary keys?  Compound is the preferred term in SQL, and there is no reason to be gratuitously different.  In fact "composite" is confusing to Thrift users because of CompositeType.

(That said, when talking about a *partition* key composed of multiple components, I have no strong preference on composite vs compound -- partly because we've moved away from easy analogies with SQL, and partly because it really is a CompositeType under the hood.  OTOH it may be best to leave Composite dead and buried and not burden CQL with extra terminology.)
                
> implement HELP  COMPOSITE_PRIMARY_KEYS
> --------------------------------------
>
>                 Key: CASSANDRA-6076
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6076
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Dave Brosius
>            Assignee: Dave Brosius
>            Priority: Trivial
>             Fix For: 1.2.11
>
>         Attachments: 6076.txt
>
>
> HELP COMPOSITE_PRIMARY_KEYS is referenced from HELP CREATE_TABLE, but doesn't exist. added.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira