Wei Deng created CASSANDRA-11628:
------------------------------------
Summary: Fix the regression to CASSANDRA-3983 that got introduced
by CASSANDRA-10679
Key: CASSANDRA-11628
URL: https://issues.apache.org/jira/browse/CASSANDRA-11628
Project: Cassandra
Issue Type: Bug
Components: Tools
Reporter: Wei Deng
It appears that the commit from CASSANDRA-10679 accidentally cancelled out the
effect that was originally intended by CASSANDRA-3983. In this case, we would
like to address the following situation:
When you already have a C* package installed (which will deploy a file as
/usr/share/cassandra/cassandra.in.sh), but also attempt to run from a binary
download from http://cassandra.apache.org/download/, many tools like
cassandra-stress, sstablescrub, etal. will search the packaged dir
(/usr/share/cassandra/cassandra.in.sh) for 'cassandra.in.sh' before searching
the dir in your binary download or source build. We should reverse the order of
that search so it checks locally first. Otherwise you will encounter some error
like the following:
{noformat}
root@node0:~/apache-cassandra-3.6-SNAPSHOT# tools/bin/cassandra-stress -h
Error: Could not find or load main class org.apache.cassandra.stress.Stress
{noformat}
{noformat}
root@node0:~/apache-cassandra-3.6-SNAPSHOT# bin/sstableverify -h
Error: Could not find or load main class
org.apache.cassandra.tools.StandaloneVerifier
{noformat}
The goal for CASSANDRA-10679 is still a good one: "For the most part all of our
shell scripts do the same thing, load the cassandra.in.sh and then call
something out of a jar. They should all look the same." But in this case, we
should correct them all to look the same but making them to look local dir
first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
