-
Notifications
You must be signed in to change notification settings - Fork 805
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
[cassandra] Expose timeout and consistency level configuration #5675
[cassandra] Expose timeout and consistency level configuration #5675
Conversation
Pull Request Test Coverage Report for Build 018f104c-e659-4aeb-806d-f0bfe091ee6bDetails
💛 - Coveralls |
3463fcf
to
f519140
Compare
Consistency: gocql.ParseConsistency(cfg.Consistency), | ||
SerialConsistency: gocql.ParseSerialConsistency(cfg.SerialConsistency), |
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.
can you change these functions to return err instead of panicing? I know toGoCqlConfig
is not returning error but it's only caller is doCreateDB
which returns error so we can propagate these errors.
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.
PR for this change: #5811
89efbd7
to
6ddc5fc
Compare
f177e99
to
6c2bd56
Compare
Codecov Report
Additional details and impacted files
... and 10 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
30bbea5
to
33836b4
Compare
e6cefc5
to
e3509ea
Compare
What changed?
Allow to change timeout and consistency levels for Cassandra connections.
Default hardcoded values will be applied if no values are provided in configuration
Why?
There was no way to change hard-coded defaults.
How did you test it?
Potential risks
Release notes
Documentation Changes