-
Notifications
You must be signed in to change notification settings - Fork 31
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
"userSetServerless" is null
error when upgrading to version 2.1.0.22
#103
Comments
@NathanEckert this should be fixed in this commit: 0ab3dac Can you please check? |
Hi @bhvkshah , I am also encountering this issue. I think the commit you linked would fix this issue, but this change doesn't seem to be included in the published |
@joatcoursera Under the releases section it does seem to include the commit linked above as part of the 2.1.0.22 release. Can you try pulling again? |
I tried but no luck :( |
@joatcoursera We have another release for version 2.1.0.23 planned for early next week. Until then can you try the workaround of setting isserverless=false as part of the connection options? |
I'll try as soon as 2.1.0.23 is out |
Hey @NathanEckert @joatcoursera driver version 2.1.0.23 is out |
Thanks, it does fix indeed the issue |
Driver version
Upgrade from driver
2.1.0.19
to2.1.0.22
Redshift version
Other dependency:
com.zaxxer:HikariCP
version5.0.1
Client Operating System
JAVA/JVM version
Problem description
Recently, I had a performance issue with
com.amazon.redshift:redshift-jdbc42
, when upgrading from version2.1.0.19
to2.1.0.20
.It was tracked by #100.
When using the newly fixed version (so bumping from
2.1.0.19
to2.1.0.22
), one single test of our test suite failed.JDBC trace logs
Reproduction code
The text was updated successfully, but these errors were encountered: