[
https://issues.apache.org/jira/browse/CASSANDRA-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019029#comment-15019029
]
Ariel Weisberg commented on CASSANDRA-10587:
--------------------------------------------
I don't think there is an issue with the data files. I think it's an issue with
sstablemetadata that your using. When I use the sstablemetadata from 2.2.2 I
don't get an an error applying it to the files you sent me.
> 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: Ariel Weisberg
> 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)
