You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2016/03/31 17:35:25 UTC

[jira] [Commented] (CASSANDRA-10587) sstablemetadata NPE on cassandra 2.2

    [ https://issues.apache.org/jira/browse/CASSANDRA-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220046#comment-15220046 ] 

Paulo Motta commented on CASSANDRA-10587:
-----------------------------------------

LGTM, tested locally and worked after fix. Thanks!

> sstablemetadata NPE on cassandra 2.2
> ------------------------------------
>
>                 Key: CASSANDRA-10587
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10587
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Tiago Batista
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.2.x, 3.x
>
>
> I have recently upgraded my cassandra cluster to 2.2, currently running 2.2.3. After running the first repair, cassandra renames the sstables to the new naming schema that does not contain the keyspace name.
>  This causes sstablemetadata to fail with the following stack trace:
> {noformat}
> Exception in thread "main" java.lang.NullPointerException
>         at org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:275)
>         at org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:172)
>         at org.apache.cassandra.tools.SSTableMetadataViewer.main(SSTableMetadataViewer.java:52)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)