Hi Benjamin,
Thanks for your suggestion.
The newest version that I found is version 22.1.1, but trying that leads to exactly the same issue.
A fragment:
20:27:22.616 |-INFO in com.dremio.jdbc.Driver - Enabling Netty native memory API for Java9+
20:27:22.921 |-INFO in c.c.dremio.common.config.SabotConfig - Configuration and plugin file(s) identified in 96ms.
Base Configuration:
- jar:file:/C:/Prog/ontop-cli/jdbc/dremio-jdbc-driver-22.1.1-202208230402290397-a7010f28.jar!/sabot-default.conf
Intermediate Configuration and Plugin files, in order of precedence:
- jar:file:/C:/Prog/ontop-cli/jdbc/dremio-jdbc-driver-22.1.1-202208230402290397-a7010f28.jar!/sabot-module.conf
20:27:23.045 |-INFO in c.o.a.arrow.memory.BaseAllocator - Debug mode disabled.
20:27:23.049 |-INFO in c.o.a.a.m.DefaultAllocationManagerOption - allocation manager type not specified, using netty as the default type
20:27:23.050 |-INFO in c.o.a.arrow.memory.CheckAllocator - Using DefaultAllocationManager at memory/DefaultAllocationManagerFactory.class
20:27:24.339 |-ERROR in c.c.d.exec.rpc.RpcExceptionHandler - Exception in RPC communication. Connection: null <--> null (user client). Closing connection.
java.lang.UnsupportedOperationException: sun.misc.Unsafe or java.nio.DirectByteBuffer.<init>(long, int) not available
(...)
But since you refer to some issues experienced with Dremio + newer Java versions in the past, I tried Java 11 anyway and that seems to solve the issue.
20:34:45.528 |-INFO in com.dremio.jdbc.Driver - Enabling Netty native memory API for Java9+
20:34:45.815 |-INFO in c.c.dremio.common.config.SabotConfig - Configuration and plugin file(s) identified in 96ms.
Base Configuration:
- jar:file:/C:/Prog/ontop-cli/jdbc/dremio-jdbc-driver-22.1.1-202208230402290397-a7010f28.jar!/sabot-default.conf
Intermediate Configuration and Plugin files, in order of precedence:
- jar:file:/C:/Prog/ontop-cli/jdbc/dremio-jdbc-driver-22.1.1-202208230402290397-a7010f28.jar!/sabot-module.conf
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by cdjd.io.netty.util.internal.ReflectionUtil (file:/C:/Prog/ontop-cli/jdbc/dremio-jdbc-driver-22.1.1-202208230402290397-a7010f28.jar) to constructor java.nio.DirectByteBuffer(long,int)
WARNING: Please consider reporting this to the maintainers of cdjd.io.netty.util.internal.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
20:34:45.981 |-INFO in c.o.a.arrow.memory.BaseAllocator - Debug mode disabled.
20:34:45.984 |-INFO in c.o.a.a.m.DefaultAllocationManagerOption - allocation manager type not specified, using netty as the default type
20:34:45.986 |-INFO in c.o.a.arrow.memory.CheckAllocator - Using DefaultAllocationManager at memory/DefaultAllocationManagerFactory.class
20:34:52.207 |-INFO in c.c.dremio.sabot.rpc.user.UserClient - [USER]: Channel closed null <--> null (user client)
R2RML mapping file jml-r2rml.ttl written!
Therefore, I guess that this is not a Ontop issue, but a Dremio one.
And - as you expected - Dremio is aware of it:
Stupid on my end not to have checked that first. Thanks for you pointing me to it.
Best regards,
Johan