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
(1)
If there are partitions for which there is no valid offset corresponding to the timestamp to seek to, the offsetForTimestamp method still includes it in the Map returned, but with a NULL value. We need to skip all partitions that have offset as NULL when subscribing to avoid an error when we try to seek to the offset at a later step.
(2)
There was a bug in the seekTo feature . In situations where there are multiple partitions on the topic and some of the partitions do not have a valid offset corresponding the timestamp to seek to, the seek operation will give an NPE.
@a1shadows, Now you have been added as a collaborator, can you please Click here- accept and join ?
(1)
If there are partitions for which there is no valid offset corresponding to the timestamp to seek to, the offsetForTimestamp method still includes it in the Map returned, but with a NULL value. We need to skip all partitions that have offset as NULL when subscribing to avoid an error when we try to seek to the offset at a later step.
(2)
There was a bug in the seekTo feature . In situations where there are multiple partitions on the topic and some of the partitions do not have a valid offset corresponding the timestamp to seek to, the seek operation will give an NPE.
More discussions are here:
#630 (comment)
The text was updated successfully, but these errors were encountered: