-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[bugfix] Handling null value for kafka client id suffix #13279
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #13279 +/- ##
============================================
+ Coverage 61.75% 62.16% +0.40%
+ Complexity 207 198 -9
============================================
Files 2436 2536 +100
Lines 133233 139401 +6168
Branches 20636 21548 +912
============================================
+ Hits 82274 86653 +4379
- Misses 44911 46259 +1348
- Partials 6048 6489 +441
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Suggest handling null
within RealtimeSegmentDataManager
constructor:
String clientIdSuffix =
instanceDataManagerConfig != null ? instanceDataManagerConfig.getConsumerClientIdSuffix() : null;
if (StringUtils.isNotBlank(clientIdSuffix)) {
_clientId = _tableNameWithType + "-" + streamTopic + "-" + _partitionGroupId + "-" + clientIdSuffix;
} else {
_clientId = _tableNameWithType + "-" + streamTopic + "-" + _partitionGroupId;
}
d35cde3
to
63979f0
Compare
Thanks for catching this @tibrewalpratik17 . |
label:
bugfix
A small follow-up fix to #13168. I recently deployed this patch to one of our clusters and found
null
getting appending to client id. This patch fixes that issue.Above if ciientIdSuffix is null, we were not substituting it with
""
.cc @Jackie-Jiang