cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4041) Allow updating column_alias types
Date Tue, 26 Jun 2012 14:57:44 GMT

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

Pavel Yaskevich commented on CASSANDRA-4041:
--------------------------------------------

Thinking about the syntax, good way probably would be to do "alter table <cf> add primary_key
'<new-column-name>'", which would add the column definition to the end of composite
comparator, what do you think? The easiest tho is to support "alter table <cf> with
comparator = '<col_1, col_2, col_3, ...>'" which would require from users to specify
all of the column names to be used in comparator or alternatively "alter table <cf>
set primary_key '<col_1, col_2, ...>".
                
> Allow updating column_alias types
> ---------------------------------
>
>                 Key: CASSANDRA-4041
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4041
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>            Reporter: Sylvain Lebresne
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 1.1.2
>
>
> CASSANDRA-3657 has added the ability to change comparators (including parts of a compositeType)
when compatible. The code of CQL3 forbids it currently however so we should lift that limitation.

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