Skip to content

Document and update integration test with the versions of Kafka Jaeger supports #3068

@Ashmita152

Description

@Ashmita152

Requirement - what kind of business use case are you trying to solve?

Update jaeger-v2 kafka integration tests to test with the two most recent versions of Kafka

Problem - what in Jaeger blocks you from solving the requirement?

Right now we don't mention anywhere in the doc the version of kafka we support. This has lead to multiple open issues: #3059 #2950 #2068

Although Sarama says "Sarama is a Go library for Apache Kafka 0.8, and up." but their functional tests only test for kafka v2.7.1 and v2.8.0.

The dependabot or other PR bump up the version of Sarama which may break integration with older version of kafka.

Proposal - what do you suggest to solve the problem or improve the existing situation?

Update kafka integration test for each kafka versions we support just like how we do for ES

Any open questions to address

This will increase the integration test time but I think we should do it to prevent unknown breaking changes.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions