-
Notifications
You must be signed in to change notification settings - Fork 641
[ISSUE #4690] Fix Kafka Connector failed to start #4691
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4691 +/- ##
=========================================
Coverage 17.39% 17.40%
- Complexity 1759 1760 +1
=========================================
Files 797 797
Lines 29850 29850
Branches 2579 2579
=========================================
+ Hits 5192 5194 +2
+ Misses 24177 24176 -1
+ Partials 481 480 -1 ☔ View full report in Codecov by Sentry. |
|
@Pil0tXia Can I create a separate pull request to address the version issue? It's recommended to handle one thing per pull request for better clarity. |
I agree this approach, each PR should not include too many changes that are not related to the PR theme. |
This reverts commit c60b559.
mxsm
left a comment
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.
LGTM
* Fix StringDeserializer & (session.timeout.ms)/3 > heartbeat.interval.ms https://stackoverflow.com/questions/38406298/why-cant-i-increase-session-timeout-ms * customize timeout config * add new versions and remove redundant line-breaks * Increase master version * Fix an operator log typo * Revert "Increase master version" This reverts commit b112290. * Revert 'add new versions for issue template'
Fixes #4690.
Motivation
#4690
Modifications
Failed to construct kafka consumererrorThe session timeout is not within the range allowed by the brokererror happened after the previous fixIncreasemasterbranch version from1.9.0-releaseto1.10.0-releaseAdd new versions for bug issue templateand remove redundant line-breaksDocumentation