[
https://issues.apache.org/jira/browse/CASSANDRA-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-10587:
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2.x)
(was: 3.x)
3.5
3.0.5
2.2.6
Status: Resolved (was: Ready to Commit)
Committed as c662259fe9e1e25e10e58eb1146de80c53e69867, 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.6, 3.0.5, 3.5
>
>
> 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)
