More helpful `OffsetOutOfRange` error
Closed this issue · 0 comments
crepererum commented
OffsetOutOfRange
may happen on two sides:
- The offset that we are trying to read was deleted (either via the API or via the retention policy)
- The offset does not exist yet (or is gone for another reason, e.g. because a topic was re-created).
Both cases are reported using the very same error code, but the FETCH response should have enough information (log start, high watermark) to determine the difference.