cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-4171) cql3 ALTER TABLE foo WITH default_validation=int has no effect
Date Wed, 18 Apr 2012 21:16:40 GMT


Jonathan Ellis resolved CASSANDRA-4171.

    Resolution: Fixed

We should raise an error for trying to use default_validation under cql3.  The right way to
model this would be something like:

    foo text,
    i   int,
    PRIMARY KEY (foo, i)

> cql3 ALTER TABLE foo WITH default_validation=int has no effect
> --------------------------------------------------------------
>                 Key: CASSANDRA-4171
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API, Core
>    Affects Versions: 1.1.0
>            Reporter: paul cannon
>            Assignee: paul cannon
>              Labels: cql3
>             Fix For: 1.1.0
> 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:!default.jspa
For more information on JIRA, see:


View raw message