This should be fixed now, https://issues.apache.org/jira/browse/HIVE-18612
is committed and new war is deployed on our ptest server.
Alan, can you please go ahead and give it another go to see if it all works
fine?
Thanks,
Adam
On 2 February 2018 at 15:42, Adam Szita wrote:
> Hi,
>
> I've taken
Hi,
I've taken a look on this, and I think the problem is that although setting
JAVA_HOME to 1.8 JDK makes maven use 1.8 java and javac, any subprocess
forked only use "java" executable which is on PATH (and not checking
JAVA_HOME value.)
And on the server that is a 1.7 JRE so I'm proposing a fix
+ Peter, Adam (The Yetus experts)
On Thu, Feb 1, 2018 at 9:49 AM, Alan Gates wrote:
> Ok, looking briefly at it, it looks like if we changed
> testutils/…/TestScripts.java line 76 to set javaHome to 1.8 instead of 1.7
> that we’ll be running ptest with 1.8. I’m not familiar with ptest, but I’m
Ok, looking briefly at it, it looks like if we changed
testutils/…/TestScripts.java line 76 to set javaHome to 1.8 instead of 1.7
that we’ll be running ptest with 1.8. I’m not familiar with ptest, but I’m
guessing that someone would need to make this change and then re-deploy
ptest in our test inf
I put code in the latest patch for HIVE-17983 that executes one of the
compiled classes as part of the maven build. (It does this to
automatically generate the config template.) This works locally and in the
ptest build. But in the Yetus tests it fails with:
Exception in thread "main" java.lang
