-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when compiling Spring Native image which depends on snowflake-jdbc #1222
Comments
I also just ran into this error. Spring Boot 3.0.1 Version info: 'GraalVM 22.3.0 Java 17 CE' <dependency>
<groupId>net.snowflake</groupId>
<artifactId>snowflake-jdbc</artifactId>
<version>3.13.26</version>
</dependency> |
The JDBC driver uses this version of google-cloud-storage: Which version you think has the fix? The actual error comes from "cannot access class com.oracle.svm.core.configure.ResourcesRegistry (in module org.graalvm.nativeimage.builder) because module org.graalvm.nativeimage.builder does not export com.oracle.svm.core.configure to unnamed module @0x5b65c6fd |
It looks to me that net.snowflake.client.jdbc.internal.google.api.gax.nativeimage.GoogleJsonClientFeature lives in the SnowFlake JDBC driver: And, it's attempting to use a class that has been encapsulated, perhaps in newer versions of GraalVM?: But from what I see the issue is within the SnowFlake JDBC driver. I think what should happen is that these resource hints should be provided via GraalVM metadata JSON files, instead of being added programmatically inside of this GraalVM Feature implementation. |
With a package like that, I would guess that the Snowflake JDBC is shadowing the library to avoid version conflicts.
Sort of both? But the SVM dependency - which is what
The latest version of |
currently |
I'm testing out GraalVM native images and hitting an error during compilation pointing at class
net.snowflake.client.jdbc.internal.google.api.gax.nativeimage.GoogleJsonClientFeature
.This seems to be included through
google-cloud-storage -> gax-java
. It also looks like newer versions ofgax-java
might have fixed this issue. Would it be possible to update the version ofgoogle-cloud-storage
used to pull in the most recent version ofgax-java
?The text was updated successfully, but these errors were encountered: