[
https://issues.apache.org/jira/browse/CASSANDRA-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511554#comment-13511554
]
David Tootill commented on CASSANDRA-5000:
------------------------------------------
Changing the serializer to a BigIntegerSerializer did not resolve the issue.
However, changing the CF to use Int32Type does work, and I no longer see the
NPE in the server or the timeout in the client.
I see you've closed the issue. I agree my personal problem is resolved, but
IMO there's still an issue in the server, as an NPE is not an appropriate
response to composite field mismatch, particularly one that that worked as
expected in previous releases. It would be better to raise an exception that
specifically cites an issue with the column name definition.
In any case, thank you very much for the quick and accurate response to my
issue.
> Null pointer exception in SecondaryIndexManager.getIndexKeyFor in Cassandra
> 1.1.x
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-5000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5000
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Environment: Linux (exact environment doesn't appear to be relevant;
> reproduced on RedHat and Centos)
> Reporter: David Tootill
> Assignee: Yuki Morishita
> Attachments: CassandraDefect5000-1.0-SNAPSHOT-1.tar.gz,
> CassandraDefect5000-1.0-SNAPSHOT-2.tar.gz, Cassandra Defect 5000 Reproduction
> and Background.docx, stdlog.txt, system.log
>
>
> Cassandra 1.1.0 and following releases gets an NPE in SecondaryIndexManager
> writing a CF with multiple secondary keys. Problem did not occur in 1.0.x,
> and can be resolved by downgrading the Cassandra server. Stack trace is:
> ERROR [MutationStage:47] 2012-11-28 11:24:30,865 AbstractCassandraDaemon.java
> (line 134) Exception in thread Thread[MutationStage:47,5,main]
> java.lang.RuntimeException: java.lang.NullPointerException
> at
> org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1254)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.db.index.SecondaryIndexManager.getIndexKeyFor(SecondaryIndexManager.java:299)
> at
> org.apache.cassandra.db.index.SecondaryIndexManager.applyIndexUpdates(SecondaryIndexManager.java:463)
> at org.apache.cassandra.db.Table.apply(Table.java:459)
> at org.apache.cassandra.db.Table.apply(Table.java:384)
> at org.apache.cassandra.db.RowMutation.apply(RowMutation.java:294)
> at
> org.apache.cassandra.service.StorageProxy$6.runMayThrow(StorageProxy.java:453)
> at
> org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1250)
> Client stack trace is:
> me.prettyprint.hector.api.exceptions.HTimedOutException: TimedOutException()
> at
> me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(ExceptionsTranslatorImpl.java:35)[hector-core-1.0-5.jar:]
> at
> me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(HConnectionManager.java:264)[hector-core-1.0-5.jar:]
> at
> me.prettyprint.cassandra.model.ExecutingKeyspace.doExecuteOperation(ExecutingKeyspace.java:97)[hector-core-1.0-5.jar:]
> at
> me.prettyprint.cassandra.model.MutatorImpl.execute(MutatorImpl.java:243)[hector-core-1.0-5.jar:]
> ... 3 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
