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

Explicity test kafka 4.0 with new default protocol version 2.1.0 #41654

Open
khushijain21 opened this issue Nov 18, 2024 · 2 comments · May be fixed by #41833
Open

Explicity test kafka 4.0 with new default protocol version 2.1.0 #41654

khushijain21 opened this issue Nov 18, 2024 · 2 comments · May be fixed by #41833
Labels
Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Comments

@khushijain21
Copy link
Contributor

khushijain21 commented Nov 18, 2024

Related to #41165

Explicity test kafka 4.0 with new default protocol version 2.1.0 and our upgraded sarama version 1.43.3
This is part of an effort to upgrade sarama and the default protocol version in filebeat to be compatible with latest 4.0 kafka version.

Kafka 4.0 is due in 2.-3 months and will be available for our testing only afterwards.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 18, 2024
@khushijain21 khushijain21 added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Nov 18, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 18, 2024
@jlind23 jlind23 linked a pull request Dec 3, 2024 that will close this issue
6 tasks
@ijuma
Copy link

ijuma commented Dec 21, 2024

The PR with the relevant changes has been merged to the 4.0 branch of Apache Kafka: apache/kafka#18291

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants