Getting around the reflective access errors might also just be a matter
of expanding the list in drill-config.sh near line 300:
# Allow reflective access on Java 9+ export
DRILLBIT_OPTS="$DRILLBIT_OPTS --add-opens
java.base/java.lang=ALL-UNNAMED" export DRILLBIT_OPTS="$DRILLBIT_OPTS
--add-opens=java.base/java.util=ALL-UNNAMED" export
DRILLBIT_OPTS="$DRILLBIT_OPTS --add-opens
java.base/sun.nio.ch=ALL-UNNAMED" export DRILLBIT_OPTS="$DRILLBIT_OPTS
--add-opens java.base/java.net=ALL-UNNAMED" export
DRILLBIT_OPTS="$DRILLBIT_OPTS --add-opens
java.base/java.nio=ALL-UNNAMED" export DRILLBIT_OPTS="$DRILLBIT_OPTS
--add-opens java.security.jgss/sun.security.krb5=ALL-UNNAMED"
On 2022/01/24 15:41, Rafael Jaimes III wrote:
I've been running Drill 1.19 on OpenJDK 17 with no issues. I do get the
same warning you mentioned, but it is not a fatal error. I think your error
hitting the Drill UI page is unrelated.
You could also try OpenJDK 11 in the meantime. It's the only JDK version
that is explicitly compatible with Drill now, and not EOL. AFAIK.
On Mon, Jan 24, 2022 at 8:18 AM James Turton <[email protected]>
wrote:
Hi
Drill 1.20 will be compatible up to at least JDK 17 and will be released
in the next week or two. One way you can preview Drill running on JDK
17 is through the master-openjdk-17
<
https://hub.docker.com/layers/apache/drill/master-openjdk-17/images/sha256-24b34ea797d51491eaaa2a2f7d292e9df7c92a636e14f8e5659f6452b08711c4?context=explore>
Docker image here:
https://hub.docker.com/r/apache/drill/tags
On 2022/01/24 13:16, Rukmani Palaniappan wrote:
Hi Team,
I was using java 8 (Jdk 8, jre 8) earlier. And For Database
connectivity with POSTMAN, I used apache driller 1.18.0 . It worked
fine. But now the java 8 version is outdated and I'm moving to java 16
(jdk 16) but apache drill is not compatible with this version of java.
Is there any solution to resolve this. I am majorly blocked with
this.
With below script I got this:
C:\Automation\apache-drill-1.19.0\bin>sqlline.bat -u
"jdbc:drill:zk=local"
Java HotSpot(TM) 64-Bit Server VM warning: Option --illegal-access is
deprecated and will be removed in a future release.
And on hittinghttps://localhost:8047/query - i m getting 405 error
