Benedict commented on CASSANDRA-6276:

3.0 storage engine won't be universal for a while (maybe never for thrift), but 
will index directly into columns (i.e. won't touch any not requested), so could 
trivially avoid retrieving data for dropped columns. The only problem is we'd 
need to track the range of sstables for which they were previously dropped (and 
maybe contains stale data), and which we now apply the new comparator too, 
which would be a bit ugly/annoying.

> CQL: Map can not be created with the same name as a previously dropped list
> ---------------------------------------------------------------------------
>                 Key: CASSANDRA-6276
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6276
>             Project: Cassandra
>          Issue Type: Bug
>         Environment:  Cassandra 2.0.2 | CQL spec 3.1.0
> centos 64 bit
> Java(TM) SE Runtime Environment (build 1.7.0-b147)
>            Reporter: Oli Schacher
>            Assignee: Benjamin Lerer
>            Priority: Minor
>              Labels: cql
>             Fix For: 2.1.1
>         Attachments: CASSANDRA-6276.txt
> If create a list, drop it and create a map with the same name, i get "Bad 
> Request: comparators do not match or are not compatible."
> {quote}
> cqlsh:os_test1> create table thetable(id timeuuid primary key, somevalue 
> text);
> cqlsh:os_test1> alter table thetable add mycollection list<text>;  
> cqlsh:os_test1> alter table thetable drop mycollection;
> cqlsh:os_test1> alter table thetable add mycollection map<text,text>;  
> Bad Request: comparators do not match or are not compatible.
> {quote}

This message was sent by Atlassian JIRA

Reply via email to