-
Notifications
You must be signed in to change notification settings - Fork 719
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add support for kafka streams new processing api #1367
add support for kafka streams new processing api #1367
Conversation
…urke/brave into kafka-streams-new-processor-api
…urke/brave into kafka-streams-new-processor-api
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.
Thanks @dermotmburke! This looks great!
I took an initial look and added some comments about naming, though I'm open to hear other opinions.
instrumentation/kafka-streams/src/main/java/brave/kafka/streams/KafkaStreamsTracing.java
Outdated
Show resolved
Hide resolved
instrumentation/kafka-streams/src/main/java/brave/kafka/streams/KafkaStreamsTracing.java
Outdated
Show resolved
Hide resolved
instrumentation/kafka-streams/src/test/java/brave/kafka/streams/ITKafkaStreamsTracing.java
Outdated
Show resolved
Hide resolved
instrumentation/kafka-streams/src/test/java/brave/kafka/streams/ITKafkaStreamsTracing.java
Outdated
Show resolved
Hide resolved
…s/KafkaStreamsTracing.java using the suggested naming convention Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
…s/KafkaStreamsTracing.java using the suggested naming convention Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
…s/ITKafkaStreamsTracing.java using the suggested naming convention Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
…s/ITKafkaStreamsTracing.java using the suggested naming convention Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
Thanks @jeqo. Yeah the naming of the new TracingProcessor didn't seem that straight forward - but as you said the encapsulation prevents the name from leaking out so I suppose it doesn't matter that much. I merged your suggested changes. |
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.
Thanks @dermotmburke. I guess you missed changing the file names :)
Once build is fixed and names aligned, we could wrap up this PR by updating the instrumentation/kafka-streams/README.md and RATIONALE.md. Let me know how you feel about adding this and if you need any help. Thanks again!
instrumentation/kafka-streams/src/main/java/brave/kafka/streams/NewTracingProcessor.java
Outdated
Show resolved
Hide resolved
instrumentation/kafka-streams/src/test/java/brave/kafka/streams/KafkaStreamsTest.java
Outdated
Show resolved
Hide resolved
Apologies @jeqo I should have checked the PR changes a bit closer :) I have updated the README.md and RATIONALE.md files as suggested. Wasn't entirely sure what changes to make so let me know if they make sense. Thanks |
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.
Thanks @dermotmburke! Left some minor comments to improve docs, but all looks good to me. Once fixed, it should be good to merge unless CI says otherwise :)
Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
Sorry - been a bit too busy with family stuff over the Easter period to look at this. All looks good to me. Thanks |
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.
thanks @dermotmburke !
Let's wait a bit if there's additional feedback from the the team, but LGTM!
Hi @jeqo - looks like there was an error running the gRPC tests - is this a known issue? |
Thanks for noticing! I don't remember to have seeing it before. but it's definitely unrelated. Retrying now, let's see if persists |
} finally { | ||
// Inject this span so that the next stage uses it as a parent | ||
kafkaStreamsTracing.injector.inject(span.context(), record.headers()); | ||
if (error != null) span.error(error); |
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 wonder why this does not happen in the catch and if we should check for noop.
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.
Interesting. Maybe we can discuss this in another issue (if it's an issue)?.
I can see we have follow this pattern on kafka-streams and kafka-clents:
brave/instrumentation/kafka-streams/src/main/java/brave/kafka/streams/TracingTransformer.java
Line 64 in 0e26fd7
if (error != null) span.error(error); brave/instrumentation/kafka-clients/src/main/java/brave/kafka/clients/TracingCallback.java
Line 41 in f924f7f
if (exception != null) span.error(exception);
} finally { | ||
// Inject this span so that the next stage uses it as a parent | ||
kafkaStreamsTracing.injector.inject(span.context(), record.headers()); | ||
if (error != null) span.error(error); |
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.
same comment as below.
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.
Thanks @dermotmburke!
Thanks @jcchavezs and @dermotmburke for the great work! |
Will ship a new release later today 🚀 |
Thanks for all the support @jeqo |
<3
…On Sun, 16 Apr 2023, 10:31 Dermot Burke, ***@***.***> wrote:
Thanks for all the support @jeqo <https://github.com/jeqo>
—
Reply to this email directly, view it on GitHub
<#1367 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXOYAWEJWEXNIQ62IGLQ3DXBOU7XANCNFSM6AAAAAAWCWU22A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Fix #1365