the time in ListOffsetRequest means different things in v0 and starting v1
In ListOffsetRequest/ListOffsetResponse v0, we return a list of offsets which is smaller than or equals to the target time.
Starting v1 (from KIP-79):
Look up the offsets for the given partitions by timestamp. The returned offset for each partition is the earliest offset whose timestamp is greater than or equals to the given timestamp in the corresponding partition. If no message has a timestamp that is greater than or equals to the target time, a null will be returned
Currently we always return earliest offset with timestamp >= timestamp is request, even tho we claim that we support v0, see schemata/list_offset_request.json
@piyushredpanda what do you think is the priority for this issue?
This came up in https://github.com/redpanda-data/redpanda/issues/4308
the
time
inListOffsetRequest
means different things inv0
and startingv1
Starting
v1
(from KIP-79):Currently we always return earliest offset with timestamp >= timestamp is request, even tho we claim that we support v0, see
schemata/list_offset_request.json
@piyushredpanda what do you think is the priority for this issue?
JIRA Link: CORE-897