[
https://issues.apache.org/jira/browse/CASSANDRA-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084919#comment-14084919
]
Aleksey Yeschenko commented on CASSANDRA-6276:
----------------------------------------------
bq. In the longer run, one way to maybe fix this would be to push
dropped_columns down to the sstable reading level. If we were skipping cells as
soon as they are deserialized before they ever hit any comparator we would be
free to update the comparator. Probably messy/inefficient to do with the
current code, but might become feasible with 3.0 storage engine changes, we'll
see.
True. Would still be tricky somewhat, given that schema updates don't propagate
instantly, but we'll see.
> 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
(v6.2#6252)
