[
https://issues.apache.org/jira/browse/CASSANDRA-12181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378818#comment-15378818
]
Robert Stupp commented on CASSANDRA-12181:
------------------------------------------
Would it be ok to just catch {{RuntimeException}} and wrap that one instead of
a new {{InvalidCustomTypeException}}?
So like this:
{code}
catch (RuntimeException e)
{
throw new RuntimeException(e.getMessage()
+ " This might due to a
mismatch between the schema and the data read for ksName: "
+ keyspace.getName() + ",
cfName: " + name, e);
}
{code}
> 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.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)
