You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
Describe the bug
Currently, KoP return wrong value when process ListOffsetRequest.
To Reproduce
start pulsar broker with KoP
send some message to broker
ListOffsetRequest for specified timstamp
Expected behavior
KoP should return the right value for ListOffsetRequest
Additional context
For example, we produce 4 message with timestamp
timestamp for message 0 is 2
timestamp for message 1 is 4
timestamp for message 2 is 6
timestamp for message 3 is 8
and do ListOffsetRequest test , offset result are following
offset for earliest 0
offset for latest 4
offset fortime 2 is 0
offset fortime 3 is 0
offset fortime 4 is 1
offset fortime 5 is 1
offset fortime 6 is 2
offset fortime 7 is 2
offset fortime 8 is 3
offset fortime 9 is 3
As we can see from the result, when timestamp is 3, 5, 7, 9, the offset result should be 1, 2, 3, 4, but found 0, ,1, 2,3
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, KoP return wrong value when process
ListOffsetRequest
.To Reproduce
ListOffsetRequest
for specified timstampExpected behavior
KoP should return the right value for
ListOffsetRequest
Additional context
For example, we produce 4 message with timestamp
and do ListOffsetRequest test , offset result are following
As we can see from the result, when timestamp is 3, 5, 7, 9, the offset result should be 1, 2, 3, 4, but found 0, ,1, 2,3
The text was updated successfully, but these errors were encountered: