[
https://issues.apache.org/jira/browse/CASSANDRA-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271934#comment-14271934
]
Jimmy Mårdell commented on CASSANDRA-8579:
------------------------------------------
We install Cassandra using the Debian package in our production environment.
Tools such as sstable2json and sstablemetadata gets installed in /usr/bin.
sstable2json works, but sstablemetadata doesn't ("Error: Could not find or load
main class org.apache.cassandra.tools.SSTableMetadataViewer") because the
CLASSPATH gets incorrectly set.
The patch above simple resolves the CLASSPATH in sstablemetadata the same way
it's resolved in sstable2json (and a few other tools).
In the source code, these tools are located in different directories in 2.0
(bin vs tools/bin) although these was fixed in 2.1. But the scripts still
resolve the CLASSPATH differently in 2.1. So the patch imho is needed in both.
> sstablemetadata can't load org.apache.cassandra.tools.SSTableMetadataViewer
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-8579
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8579
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Jimmy Mårdell
> Assignee: Jimmy Mårdell
> Priority: Minor
> Fix For: 2.0.12, 2.1.3
>
> Attachments: cassandra-2.0-8579-1.txt, cassandra-2.1-8579-1.txt
>
>
> The sstablemetadata tool only works when running from the source tree. The
> classpath doesn't get set correctly when running on a deployed environment.
> This bug looks to exist in 2.1 as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
