Skip to content
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

Merged
merged 19 commits into from
Apr 14, 2023

Conversation

dermotmburke
Copy link
Contributor

@dermotmburke dermotmburke commented Mar 21, 2023

Fix #1365

@dermotmburke dermotmburke marked this pull request as draft March 21, 2023 16:45
Copy link
Member

@jeqo jeqo left a 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.

dermotmburke and others added 4 commits March 30, 2023 14:02
…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>
@dermotmburke
Copy link
Contributor Author

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.

Copy link
Member

@jeqo jeqo left a 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!

@dermotmburke
Copy link
Contributor Author

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

@dermotmburke dermotmburke requested a review from jeqo April 5, 2023 17:23
Copy link
Member

@jeqo jeqo left a 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 :)

@jcchavezs jcchavezs requested a review from shakuzen April 5, 2023 21:40
dermotmburke and others added 2 commits April 9, 2023 08:31
Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
Co-authored-by: Jorge Esteban Quilcate Otoya <jorge.quilcate@aiven.io>
@dermotmburke
Copy link
Contributor Author

Sorry - been a bit too busy with family stuff over the Easter period to look at this. All looks good to me. Thanks

Copy link
Member

@jeqo jeqo left a 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!

@dermotmburke
Copy link
Contributor Author

Hi @jeqo - looks like there was an error running the gRPC tests - is this a known issue?

@jeqo
Copy link
Member

jeqo commented Apr 12, 2023

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);
Copy link
Contributor

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.

Copy link
Member

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:

} 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);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comment as below.

Copy link
Contributor

@jcchavezs jcchavezs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dermotmburke!

@jeqo
Copy link
Member

jeqo commented Apr 14, 2023

Thanks @jcchavezs and @dermotmburke for the great work!

@jeqo jeqo merged commit c455de9 into openzipkin:master Apr 14, 2023
@jeqo
Copy link
Member

jeqo commented Apr 14, 2023

Will ship a new release later today 🚀

@dermotmburke dermotmburke deleted the kafka-streams-new-processor-api branch April 16, 2023 08:30
@dermotmburke
Copy link
Contributor Author

Thanks for all the support @jeqo

@jcchavezs
Copy link
Contributor

jcchavezs commented Apr 16, 2023 via email

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

KafkaStreamsTracing update to align with new Kafka Streams API
3 participants