Since the replicated snapshots updates only triggered by the ack events, the PR adjusted the commit behavoid of the pulsar sub tracker (from seeking to acking) for allowing the tracker cursor to be albe to replicate to the remote clusters.
What was done:
updated the pulsar sub trackers.
upgraded the pulsar-go-client to v0.10.0 (since the AckIDCumulative is not supported before v0.10.0).
replaced the streamnative/pulsarctl with the streamnative/pulsar-admin-go (since it looks like the streamnative are now migrating the admin client implementations to the pulsar-admin-go package).
Description
Since the replicated snapshots updates only triggered by the ack events, the PR adjusted the commit behavoid of the pulsar sub tracker (from seeking to acking) for allowing the tracker cursor to be albe to replicate to the remote clusters.
What was done:
Related Document
https://github.com/apache/pulsar/wiki/PIP-33:-Replicated-subscriptions#proposed-solution