Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-987122 Upgrade JDBC to 3.14.5 and Catch new exception type for r… #677
SNOW-987122 Upgrade JDBC to 3.14.5 and Catch new exception type for r… #677
Changes from 9 commits
6a3df2e
cf7e289
0bec90d
422fbaf
7d273f9
cd7d161
1d16b9f
5e4d15d
602e281
2e402f3
460bfff
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like the fix of https://github.com/snowflakedb/snowflake-sdks-drivers-issues-teamwork/issues/819 is
on its way, could we wait for it and don't do the tricks with large strings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, we can wait now that it is pushed. but we will have to wait til next release of JDBC.
are we okay with that @sfc-gh-xhuang ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me see when next release of JDBC is.
https://snowflake.slack.com/archives/C054J469AN4/p1707957136445859
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even if they release next week, there's no guarantees it will be a simple upgrade either.
The large strings issue only affects reads and this test, it doesn't affect write behavior which is the only thing we use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1. We are just a bystander for that bug. It is not in our code and they were able to reproduce it themselves. I support not waiting for that fix to land.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JDBC plans to release next week but please consider the trade off of trying to use 3.14.6 vs today's 3.14.5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can move out the log below? Also we need to improve the log since logging only message might miss some information
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is preferable since this is indicating it is refreshing metadata. I can add stacktrace but that would be too much on every attempt.
We are already printing your suggested log line below.