[
https://issues.apache.org/jira/browse/CASSANDRA-12181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383778#comment-15383778
]
Sylvain Lebresne commented on CASSANDRA-12181:
----------------------------------------------
Thanks for the stack. I still kind of feel this shouldn't be happening at that
point, we should have somehow validated the mutation against the schema and/or
the schema change earlier, but it's hard to say without more context and
knowing what led to this. I suppose there is no harm in getting a more helpful
exception when that happen though so I'm good with v3 and feel free to let us
know if you find more details on the original cause for this so we can improve
the experience.
> 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-v3.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)
