Revision aa51b0bd36d8a016fbf5be9244a8ba28b1b64fe8 authored by ARUNACHALAM THIRUPATHI on 30 June 2015, 21:47:13 UTC, committed by ARUNACHALAM THIRUPATHI on 30 June 2015, 21:47:13 UTC
Thanks for the fix @dallasmarlow update coordinator class name in server script
voldemort-scala-shell.sh
#!/bin/bash
#
# Copyright 2008-2013 LinkedIn, Inc
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
export scala_shell="voldemort.VoldemortScalaShell"
base_dir="$( cd "$( dirname "${BASH_SOURCE[0]}" )"/.. && pwd )"
for file in $base_dir/lib/*.jar;
do
CLASSPATH=$CLASSPATH:$file
done
for file in $base_dir/contrib/*/lib/*.jar;
do
CLASSPATH=$CLASSPATH:$file
done
for file in $base_dir/dist/*.jar;
do
CLASSPATH=$CLASSPATH:$file
done
CLASSPATH=$CLASSPATH:$base_dir/dist/resources
# add '-Dlog4j.debug ' to debug log4j issues.
LOG4JPROPERTIES="-Dlog4j.configuration=file://${base_dir}/src/java/log4j.properties"
# If it is the scala shell is being launched use the scala command else java
export CLASSPATH
scala $LOG4JPROPERTIES -cp $CLASSPATH $scala_shell $@
Computing file changes ...