Open akashkhamkarr opened 2 weeks ago
Hi @akashkhamkarr,
Thanks for creating the issue. Is there anything else you can do to try and narrow down the problem? For example, is it feasible for you to run that test on specific tables, or schemas at least? Was this working on a version older than 3.16.1, or did you just happen to run this code starting with that version? In the meantime, I'll take a look to see what I can figure out based on that error stack you shared.
@sfc-gh-wfateem Hi, i was able to figure out for which data type its happening
So far its happening over the structured objects columns
steps to reproduce
.getColumns(databaseName, null, null, null)
@sfc-gh-wfateem any updates on this ?
Please answer these questions before submitting your issue. In order to accurately debug the issue this information is required. Thanks!
What version of JDBC driver are you using? 3.16.1
What operating system and processor architecture are you using? NA
What version of Java are you using? 11
What did you do? a. Fetched database columns using
connection.metaData.getColumns(databaseName, null, null, null)
b. Kept iterating over the rsjdbcResultSet
, during which i calledrs.next()
to check if any more rows are left. c. Here i got the exceptionNo enum constant net.snowflake.client.jdbc.SnowflakeType.
For the time being, we can't check the actual column data type on the snowflake, for which this has happened
Relevant stacktrace:
I believe the datatype being received is empty
What did you expect to see? a. either a default datatype value to get assign to such empty fields, or a proper parsing of the correct datatype
Can you set logging to DEBUG and collect the logs? a. Can try if required https://community.snowflake.com/s/article/How-to-generate-log-file-on-Snowflake-connectors
What is your Snowflake account identifier, if any? (Optional) NA