Fix the issue of `fetchStreamPartitionOffset` method in Kafka 2.0 implementation
Open
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
Kafka 2.0 implementation of `StreamMetadataProvider.fetchStreamPartitionOffset()` returns the next offset after the last available offset while all other implementations correctly return the last available offset. This needs to be fixed. This causes issues on startup when offset based consumption status checker is used.
Contributor guide
Research direction
Locate the Kafka 2.0 implementation of StreamMetadataProvider.fetchStreamPartitionOffset() and compare its offset handling with the other implementations. Confirm that it returns the last available offset rather than the next offset, then verify that offset-based consumption startup no longer encounters the reported issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100