linkedin / linkedin/kafka-tools
Support for different Kafka versions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 599
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
The Client only supports a single Kafka version (currently mapped to 0.10.2). It should have a configuration to select the version of the client to support, and use the appropriate versions of requests. For reference, here are the requests supported:
```
0.8.0
TopicMetadata (v0)
ListOffset (v0)
0.8.1.1
TopicMetadata (v0)
ListOffset (v0)
OffsetCommit (v0)
OffsetFetch (v0)
0.8.2.2
TopicMetadata (v0)
ListOffset (v0)
OffsetCommit (v1)
OffsetFetch (v1) (v0 reads from ZK, v1 from Kafka)
GroupCoordinator (v0) (was called ConsumerMetadata)
0.9.0.1
TopicMetadata (v0)
ListOffset (v0)
OffsetCommit (v2)
OffsetFetch (v1) (v0 reads from ZK, v1 from Kafka)
GroupCoordinator (v0)
0.10.0.0
TopicMetadata (v1)
ListOffset (v0)
OffsetCommit (v2)
OffsetFetch (v1) (v0 reads from ZK, v1 from Kafka)
GroupCoordinator (v0)
DescribeGroups (v0)
0.10.1.1
TopicMetadata (v2)
ListOffset (v1)
OffsetCommit (v2)
OffsetFetch (v1) (v0 reads from ZK, v1 from Kafka)
GroupCoordinator (v0)
DescribeGroups (v0)
0.10.2.1
TopicMetadata (v2)
ListOffset (v1)
OffsetCommit (v2)
OffsetFetch (v1) (v0 reads from ZK, v1 from Kafka)
GroupCoordinator (v0)
DescribeGroups (v0)
0.11.0.0
TopicMetadata (v4)
ListOffset (v2)
OffsetCommit (v2)
OffsetFetch (v2) (v0 reads from ZK, v1 from Kafka)
FindCoordinator (v1)
DescribeGroups (v1)
1.0.0
TopicMetadata (v5)
ListOffset (v2)
OffsetCommit (v3)
OffsetFetch (v3) (v0 reads from ZK, v1 from Kafka)
FindCoordinator (v1)
DescribeGroups (v1)
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the client’s current Kafka version mapping and request definitions. Compare that implementation with the compatibility matrix in the issue, then define what configuration selects a Kafka version and what “done” means for using the corresponding request versions across the listed releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100