-
Notifications
You must be signed in to change notification settings - Fork 167
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
SNOW-379300: Exception when switching from jdk 15 to jdk 16 #533
Comments
This StackOverflow answer solved the problem for me. Specifically, execute this prior to querying: ALTER SESSION SET JDBC_QUERY_RESULT_FORMAT='JSON' |
Starting the JVM with |
Thank you for the workaround ! |
Hello, |
This is blocked by https://issues.apache.org/jira/browse/ARROW-12747 Maybe allowing to set the result format in the connection string can help ? |
Yes. I think that will help |
Java17 is now GA'd. So is there an ETA on snowflake support or atleast correct their requirement statement: The Snowflake JDBC driver requires Java 1.8 or higher. to: |
any updates on this ? |
@sfc-gh-wfateem will you be able to provide the ETA on this? |
Hi @iamzafar, It's actually the code responsible for the problem. In the meantime, you can work around this in JDK 16 by adding the following JVM argument to your application: This will not work unfortunately in JDK 17 because they finally removed that altogether. |
@iamzafar it looks like you can also work around this in JDK 17 by adding the following Java option: |
Hi @sfc-gh-wfateem, |
I'm looking into this @iamzafar |
I cloned that PR locally and tested it. It doesn't work. The error I got was: Now MemoryUtil in Arrow is using reflection. |
communications link failure |
The ARROW-12747 blocker was finally resolved: #589 (comment) |
That's great news ! |
You can add the following 2 settings in the following file (macOS) -Djdk.module.illegalAccess=permit Information from: https://support.dbvis.com/support/solutions/articles/1000309803-snowflake-fail-to-retrieve-row-count-for-first-arrow-chunk- Another alternative that worked for me on my MAC M1, is to use JDK11 brew install openjdk@11 Edit: /Applications/DBeaver.app/Contents/Eclipse/dbeaver.ini this line: Restart dbeaver |
The issue can be marked as resolved since 3.13.19 snowflake-jdbc driver version. |
Still doesn't work for me with AdoptOpenJDK 16 @vkopichenko |
Oh. It seems I got deceived by long-awaited eager expectations. We'll have to await a bit more for another Arrow upgrade from 7.0.0 to 8.0.0: #589 (comment) |
This should be addressed in #1017 |
It would be awesome to get a new release off of |
After upgrading to 3.13.20 we are still seeing errors with JDK 17
|
Yes, I can confirm that the problem still occurs. Not sure what happened here, because Apache Arrow highlighted that this was fixed in 8.0. We'll need to dig into this a bit more. |
Hi @sfc-gh-wfateem , Another customer also reported the same problem. I mentioned details in JIRA SNOW-379300. Thanks, |
It looks like that fix in Arrow v8.0 was just simply a workaround: |
can confirm that M1 CPU, snowflake jdbc [3.13.21] and jre17 (i.e. dbeaver Version 22.1.3.202207240747) still not functional. might be because pom.xml for snowflake jdbc 3.13.21 still shows: -> related to: SNOW-349075: Upgrade JNA to support arm64-macos architecture |
Same here, got this error on JDK 17 |
Hello @sfc-gh-wfateem, do you have any ETA about this ? |
Apache Arrow are not going to fix it. You can switch to using JSON in response, but I'll assume for huge selects it will work slower and network load will be higher. |
Root cause: snowflakedb/snowflake-jdbc#533 Co-authored-by: Dzmitry Katsechau <Dzmitry_Katsechau@epam.com>
Please follow-up using #589. So closing this issue as both are similar issues and comments. If anyone feels otherwise, please reopen it. |
I'm running a simple query with the snowflake jdbc.
it is working with the jdk 15. When I try with the jdk 16 I'm facing the following exception:
The text was updated successfully, but these errors were encountered: