-
Notifications
You must be signed in to change notification settings - Fork 804
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
Bump gocql version to v1.7.0 #6511
base: master
Are you sure you want to change the base?
Bump gocql version to v1.7.0 #6511
Conversation
7e24985
to
a338232
Compare
e9c04db
to
10ff970
Compare
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.
internally we are still on this old version in monorepo. Though, looking at release notes, there aren't many important behavioral changes.
|
||
// even if null is stored in cassandra, gocql will return empty struct instead of nil | ||
if version == 0 && numRead == 0 && numWrite == 0 { | ||
return nil | ||
} | ||
|
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.
I'm kinda assuming this is a change in behavior? I don't really see it in the changelog, but I might just lack gocql-context / keyword-guessing-ability to find it: https://github.com/apache/cassandra-gocql-driver/blob/trunk/CHANGELOG.md
If this is a broad "was null -> now empty struct" change, we'll probably have to do this kinda carefully :\ and/or wrap gocql and convert it everywhere, if that's possible. seems like the sort of change that'd cause a lot of minor and hard-to-notice bugs.
What changed?
Bumping gocql to the newest release
Why?
How did you test it?
Potential risks
Release notes
Documentation Changes