-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pulsar-client-cpp] Support Seek on Partitioned Topic by Time #7198
[pulsar-client-cpp] Support Seek on Partitioned Topic by Time #7198
Conversation
} | ||
stateLock.unlock(); | ||
for (ConsumerList::const_iterator i = consumers_.begin(); i != consumers_.end(); i++) { | ||
(*i)->seekAsync(msgId, callback); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The message id is only relative to 1 partition. Seeking with same message id on multiple partition will position the subscription in the wrong position.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understood that.
This PR decides to support only seeking on partitioned topic by time.
callback(ResultOperationNotSupported); | ||
Lock stateLock(mutex_); | ||
if (state_ != Ready) { | ||
callback(ResultAlreadyClosed); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The mutex should be released before triggering the callback, since that might be blocking
/pulsarbot run-failure-checks |
1 similar comment
/pulsarbot run-failure-checks |
Modifications
Support seek on partitioned topic.
Verifying this change