You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2013/12/17 17:35:09 UTC

[jira] [Commented] (CASSANDRA-2812) Allow changing comparator between compatible collations

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

Nicolas Lalevée commented on CASSANDRA-2812:
--------------------------------------------

I tried to find out if Cassandra can or will support changing the comparator type, and the only reference to a such feature I have found is that Jira issue. So I am logging here what I have found out, in case some other people are walking by this.
As far as I can see (the code), Cassandra 1.2 does support it, but the types have be the same sort algorithm (obviously), but also have compatible validators.
For instance in my use case where I want to fix a mistake where I specified the 'byte' type instead of the 'utf8' type, even if utf8 sorting is the same as the byte one, and even if all my clients are encoding in utf8, Cassandra is conservative and refuses to do the migration (be safer than sorry).

> Allow changing comparator between compatible collations
> -------------------------------------------------------
>
>                 Key: CASSANDRA-2812
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2812
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Priority: Minor
>         Attachments: 2812.txt
>
>
> Normally we should not allow changing comparators, but anything that sorts in lexical byte order (Bytes, Ascii, UTF8, LexicalUUID) is compatible.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)