cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4171) cql3 ALTER TABLE foo WITH default_validation=int has no effect
Date Fri, 20 Apr 2012 10:26:43 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne updated CASSANDRA-4171:
----------------------------------------

    Attachment: 4171.txt

I believe the correct fix is to reset the set of obsolete keywords for CQL3. We've used that
in CLQ2 for keywords to ignore (by opposition to reject) that became obsolete in order to
ensure backward compatibility. But CQL3 is not backward compatible anyway so we should start
afresh.
                
> cql3 ALTER TABLE foo WITH default_validation=int has no effect
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-4171
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4171
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API, Core
>    Affects Versions: 1.1.0
>            Reporter: paul cannon
>            Assignee: Sylvain Lebresne
>            Priority: Trivial
>              Labels: cql3
>             Fix For: 1.1.0
>
>         Attachments: 4171.txt
>
>
> running the following with cql3:
> {noformat}
> CREATE TABLE test (foo text PRIMARY KEY) WITH default_validation=timestamp;
> ALTER TABLE test WITH default_validation=int;
> {noformat}
> does not actually change the default validation type of the CF. It does under cql2.
> No error is thrown. Some properties *can* be successfully changed using ALTER WITH, such
as comment and gc_grace_seconds, but I haven't tested all of them. It seems probable that
default_validation is the only problematic one, since it's the only (changeable) property
which accepts CQL typenames.

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