Skip to content

[fix][client] Fix Reader.hasMessageAvailable return wrong value after seeking by timestamp with startMessageIdInclusive #21661

[fix][client] Fix Reader.hasMessageAvailable return wrong value after seeking by timestamp with startMessageIdInclusive

[fix][client] Fix Reader.hasMessageAvailable return wrong value after seeking by timestamp with startMessageIdInclusive #21661

Annotations

9 warnings

CI - Unit - Pulsar IO - Elastic Search

succeeded Oct 23, 2024 in 13m 37s