[
https://issues.apache.org/jira/browse/CASSANDRA-12181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381884#comment-15381884
]
Sylvain Lebresne commented on CASSANDRA-12181:
----------------------------------------------
Nit: can we at least replace {{"cfName"}} by {{"tableName"}} in the error
message (or, better, just us {{"ks"}} and {{"table"}})?
Must also say that the placement of that catch/rethrow is pretty random: I
highly doubt this is the only place this exception can be triggered. In fact,
it's slightly weird that the message talk about "reading" when this is clearly
catching a put in the memtable. Could we maybe have the full stack trace that
has made you pick that place for catching the exception so we can see if there
isn't a better place for this (typically, if this happens during commit log
replay, maybe we should catch that earlier, and if this happen during a
"normal" mutation, then maybe we should fail the original query with a
FailureException)?
> Include table name in "Cannot get comparator" exception
> -------------------------------------------------------
>
> Key: CASSANDRA-12181
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12181
> Project: Cassandra
> Issue Type: Improvement
> Reporter: sankalp kohli
> Assignee: sankalp kohli
> Priority: Trivial
> Attachments: CASSANDRA-12181-3.0_v2.txt, CASSANDRA-12181_3.0.txt
>
>
> Having table name will help in debugging the following exception.
> ERROR [MutationStage:xx] CassandraDaemon.java (line 199) Exception in thread
> Thread[MutationStage:3788,5,main]
> clusterName=itms8shared20
> java.lang.RuntimeException: Cannot get comparator 2 in
> org.apache.cassandra.db.marshal.CompositeType(org.apache.cassandra.db.marshal.UTF8Type,org.apache.cassandra.db.marshal.UTF8Type).
>
> This might be due to a mismatch between the schema and the data read
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
