[GitHub] [pulsar] mattisonchao commented on pull request #16545: PIP-187: Add API to analyze a subscription backlog and provide a accurate value

[GitBox <gi...@apache.org>]

mattisonchao commented on PR #16545:
URL: https://github.com/apache/pulsar/pull/16545#issuecomment-1187601011

   Hi, I have a concern about it.
   
   If the topic has some producers continue producing messages. Is it better to use the `timestamp` to get the backlog?
   The user doesn't need to set the `maxEntries`. If the user does not pass the timestamp, the broker will use the current time to search. If the user provides it, we will continue searching until the satisfying `timestamp` or `timeout`
   Because in the current implementation, if the admin wants to get the precious backlog, they will first search the topic, have how many un-acked entries and then get backlog. They have to use to step to get it.
   But if they use a timestamp, they no longer need to care about `maxEntries`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org