Skip to content

Conversation

@paulojmdias
Copy link
Member

@paulojmdias paulojmdias commented Aug 21, 2025

Description

This PR moves the receiver.kafkareceiver.UseFranzGo feature gate to Beta, as it also improves the tests to work with both libraries (sarama and franz-go) while the feature gate is enabled by default.

Link to tracking issue

Fixes #42155

Testing

Improved the tests to work with both libraries (sarama and franz-go) while the feature gate is enabled by default.

Documentation

Updated the README.md with the reference for the users to opt out of using franz-go, disabling the feature gate.

@paulojmdias paulojmdias marked this pull request as ready for review August 22, 2025 09:58
@paulojmdias paulojmdias requested review from a team and MovieStoreGuy as code owners August 22, 2025 09:58
@github-actions github-actions bot requested review from axw and pavolloffay August 22, 2025 09:58
Copy link
Contributor

@axw axw left a comment

Choose a reason for hiding this comment

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

Thanks @paulojmdias!

The main issue is that TestComponentStatus is not really testing anything in the franz-go path: it always hits the deadline (without failing!) because we're not reporting component status.

Is that something you can look into?

@paulojmdias
Copy link
Member Author

Thanks @paulojmdias!

The main issue is that TestComponentStatus is not really testing anything in the franz-go path: it always hits the deadline (without failing!) because we're not reporting component status.

Is that something you can look into?

Sure @axw! I'll look at all of your comments as soon as I can!

Signed-off-by: Paulo Dias <[email protected]>
@paulojmdias
Copy link
Member Author

paulojmdias commented Aug 27, 2025

@axw, I removed the featuregate tests from TestComponentStatus. I also updated the tests to support Profiles, which were added in #41479.

I tested it locally, and the tests are green, but please review it 🙏

Copy link
Contributor

@axw axw left a comment

Choose a reason for hiding this comment

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

Looks great, thank you for iterating on it @paulojmdias!

I'm not 100% sure about the component status events we report, but same goes for Sarama. I think keeping parity is good for now, and we can revisit it alter.

I'd like to get to the bottom of #42226 before we merge this.

@paulojmdias
Copy link
Member Author

Thank you @axw! 🙏

@axw axw removed the Stale label Sep 17, 2025
@axw
Copy link
Contributor

axw commented Sep 25, 2025

@paulojmdias ICYMI, seems the tests are failing now. I think that since #42226 is merged, once tests are green we can mark this as ready to merge.

@paulojmdias
Copy link
Member Author

@axw I'm looking into fixing it now 👀

@paulojmdias
Copy link
Member Author

@axw you can look into it now.

The check-codeowners check is globally failing, but I think it is related to some token issue (maybe expiration?). I already left a Slack message for discussion.

Copy link
Contributor

@axw axw left a comment

Choose a reason for hiding this comment

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

Thanks @paulojmdias. I think there's a problem with the StatusOK bit, and some possible redundant code, but otherwise it looks good.

Copy link
Contributor

@axw axw left a comment

Choose a reason for hiding this comment

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

Thank you :)

I'm not certain if updating status on each assignment is the best, but it's along the lines of what the Sarama code is doing, and I think it's fine. Maybe we can find another way to go about it later, e.g. using franz-go's hooks.

@axw axw added ready to merge Code review completed; ready to merge by maintainers and removed waiting-for-code-owners labels Sep 25, 2025
@paulojmdias
Copy link
Member Author

@axw Should we open an issue to revisit this later on?

@axw
Copy link
Contributor

axw commented Sep 26, 2025

@paulojmdias sounds good, done: #43001

@songy23 songy23 merged commit 0996c87 into open-telemetry:main Sep 26, 2025
185 checks passed
@github-actions github-actions bot added this to the next release milestone Sep 26, 2025
@paulojmdias paulojmdias deleted the feat/42155 branch September 26, 2025 14:07
songy23 pushed a commit that referenced this pull request Oct 10, 2025
#### Description

I would like to propose adding @paulojmdias as a code owner of the Kafka
components. He has been doing excellent work across all of those
components (and more besides!).

-
#42507
-
#42796
-
#43105
-
#42181
-
#42327
-
#42507
-
#42796
-
#43019
-
#43083
-
#43105

#### Link to tracking issue

N/A

#### Testing

N/A

#### Documentation

N/A
ChrsMark pushed a commit to ChrsMark/opentelemetry-collector-contrib that referenced this pull request Oct 20, 2025
#### Description

I would like to propose adding @paulojmdias as a code owner of the Kafka
components. He has been doing excellent work across all of those
components (and more besides!).

-
open-telemetry#42507
-
open-telemetry#42796
-
open-telemetry#43105
-
open-telemetry#42181
-
open-telemetry#42327
-
open-telemetry#42507
-
open-telemetry#42796
-
open-telemetry#43019
-
open-telemetry#43083
-
open-telemetry#43105

#### Link to tracking issue

N/A

#### Testing

N/A

#### Documentation

N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Code review completed; ready to merge by maintainers receiver/kafka

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[receiver/kafka] use franz-go client by default

7 participants