-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Configurable kafka protocol version for msg consuming by jaeger ingester #1640
Configurable kafka protocol version for msg consuming by jaeger ingester #1640
Conversation
5fd0fef
to
c70f284
Compare
Codecov Report
@@ Coverage Diff @@
## master #1640 +/- ##
==========================================
+ Coverage 98.71% 98.71% +<.01%
==========================================
Files 193 193
Lines 9228 9233 +5
==========================================
+ Hits 9109 9114 +5
Misses 91 91
Partials 28 28
Continue to review full report at Codecov.
|
Signed-off-by: Chodor Marek <marek.chodor@grupawp.pl>
a9def7d
to
1542008
Compare
…onfig Signed-off-by: Chodor Marek <marek.chodor@grupawp.pl>
8b2ff4b
to
8cd8860
Compare
tests are failing
|
Signed-off-by: Chodor Marek <marek.chodor@grupawp.pl>
123f92e
to
aebc038
Compare
@yurishkuro I made a typo in test data config. Fixed now. |
Q: wouldn't a symmetric change in producer code make sense as well? |
Yes. Good point. I can prepare some PR for cmd/collector pkg/kafka/producer tomorrow |
Which problem is this PR solving?
Jaeger ingester silently doesn't consume messages, when kafka server doesn't support kafka protocol in version 0.0.9.
Short description of the changes
I added new
kafka.consumer.protocol-version
configuration option, that allows specify kafka protocol version to use. Default is "0.9.0.0" which was used by bsm/sarama-cluster as default version (for backwards compatibility).