Hello Tommaso
Can you give the full exception stack trace? Consider also filing a JIRA,
it looks pretty fishy...
On Sun, Oct 12, 2014 at 10:53 PM, tommaso barbugli <tbarbu...@gmail.com>
wrote:
> Hi,
> it actually seems to be worse than what I thought; I get an exception in
> cassandra logs every time I try to create a new table.
>
> Cql query:
> CREATE TABLE shard12 ("feed_id" ascii, "activity_id" timeuuid,
> "activities" blob, "created_at" timestamp, "group" ascii, "updated_at"
> timestamp, "seen_at" timestamp, "read_at" timestamp, PRIMARY KEY
> (("feed_id"), "activity_id")) WITH read_repair_chance = 0.1 AND clustering
> order by ("activity_id" desc) AND compaction = {'sstable_size_in_mb': 64,
> 'class': 'LeveledCompactionStrategy'};
>
> This is the error:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ConfigurationException: comparators do not
> match or are not compatible.
>
> Tommaso
>
> 2014-10-12 13:05 GMT+02:00 tommaso barbugli <tbarbu...@gmail.com>:
>
>> Hi,
>> I am seeing errors every time I make a schema migration of this kind on
>> cassandra 2.0.10
>>
>> ALTER TABLE notifications add "unread_ids" set<timeuuid> static
>>
>> <ErrorMessage code=0000 [Server error]
>> message="java.lang.RuntimeException:
>> java.util.concurrent.ExecutionException: java.lang.RuntimeException:
>> org.apache.cassandra.exceptions.ConfigurationException: comparators do not
>> match or are not compatible.">
>>
>> Weird enough DESCRIBE COLUMNFAMILY notifications; shows that the column
>> unread_ids is created after the error.
>>
>> Any idea if this is an actual bug or if I am doing something wrong?
>>
>> Tommaso
>>
>
>
