[
https://issues.apache.org/jira/browse/IMPALA-14481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030116#comment-18030116
]
ASF subversion and git services commented on IMPALA-14481:
----------------------------------------------------------
Commit 7e34cabed7876b90a415f9379725fa2e27383379 in impala's branch
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=7e34cabed ]
IMPALA-14481: Use $JAVA instead of java in run-iceberg-rest-server.sh
Using the plain 'java' command in run-iceberg-rest-server.sh might
result in using a different Java version than what we used for
compilation.
$JAVA is set in bin/impala-config.sh to the desired Java version,
and we should use it in our scripts instead of just using 'java'.
Change-Id: I5f9c21de4c85d38dca7690fc110c4c44448840ed
Reviewed-on: http://gerrit.cloudera.org:8080/23539
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> REST catalog in the minicluster fails to come up in a JDK17 build because of
> class file format mismatch errors
> --------------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-14481
> URL: https://issues.apache.org/jira/browse/IMPALA-14481
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 5.0.0
> Reporter: Laszlo Gaal
> Assignee: Zoltán Borók-Nagy
> Priority: Critical
>
> In builds executed fully in a JDK17-based environment the Iceberg REST
> catalog fails to come up in the minicluster, throwing the below exceptions:
> {code}
> Picked up JAVA_TOOL_OPTIONS:
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> org/apache/iceberg/rest/IcebergRestCatalogTest has been compiled by a more
> recent version of the Java Runtime (class file version 61.0), this version of
> the Java Runtime only recognizes class file versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:621){code}
> This looks like the REST catalog wanting to start up using a Java 8 JRE (for
> unknown reasons) while using Java17 jars.
> This of course fails all the REST catalog tests during CUSTOM_CLUSTER tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
