Support both JDBC v3 and v2 driver #17
Merged
Merged
Conversation
zaneli
requested changes
Aug 9, 2025
zaneli
left a comment
Owner
There was a problem hiding this comment.
Thank you!
I also thought that hard-coded predefined config parameters was unnecessary, and I wanted to fix that. 🙏
Co-authored-by: Shunsuke Otani <shun.otani@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #16
Connection Parameters
I've compared v3 doc with v2 doc.
There are several breaking change: Some v2 parameters does not work on v3
Many parameters were added in v3, such as DataZone IdC credentials.
So I think pass-through is the simplest, most robust solution to support both v2 and v3.