[
https://issues.apache.org/jira/browse/DRILL-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krystal closed DRILL-5208.
--------------------------
commit id: 3dfb497293a177164a158b246000ee8291ef258c
On my two nodes where the order of the paths to the java executable are
different:
find -L $JAVA_HOME -name java -type f
/usr/local/java/jdk1.7.0_67/jre/bin/java
/usr/local/java/jdk1.7.0_67/bin/java
find -L $JAVA_HOME -name java -type f
/usr/local/java/jdk1.7.0_67/bin/java
/usr/local/java/jdk1.7.0_67/jre/bin/java
Now, the paths of the java executable on the two nodes are pointing to the same
location: /usr/local/java/jdk1.7.0_67//bin/java
> Finding path to java executable should be deterministic
> -------------------------------------------------------
>
> Key: DRILL-5208
> URL: https://issues.apache.org/jira/browse/DRILL-5208
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Affects Versions: 1.10.0
> Reporter: Krystal
> Assignee: Paul Rogers
> Priority: Minor
> Labels: ready-to-commit
> Fix For: 1.10.0
>
>
> Command to find JAVA in drill-config.sh is not deterministic.
> drill-config.sh uses the following command to find JAVA:
> JAVA=`find -L "$JAVA_HOME" -name $JAVA_BIN -type f | head -n 1`
> On one of my node the following command returned 2 entries:
> find -L $JAVA_HOME -name java -type f
> /usr/local/java/jdk1.7.0_67/jre/bin/java
> /usr/local/java/jdk1.7.0_67/bin/java
> On another node, the same command returned entries in different order:
> find -L $JAVA_HOME -name java -type f
> /usr/local/java/jdk1.7.0_67/bin/java
> /usr/local/java/jdk1.7.0_67/jre/bin/java
> The complete command picks the first one returned which may not be the same
> on each node:
> find -L $JAVA_HOME -name java -type f | head -n 1
> /usr/local/java/jdk1.7.0_67/jre/bin/java
> If JAVA_HOME is found, we should just append the "bin/java" to the path"
> JAVA=$JAVA_HOME/bin/java
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
