sajjad-moradi commented on issue #7850:
URL: https://github.com/apache/pinot/issues/7850#issuecomment-985080568


   We have seen some use cases for which the stream has a bursty traffic 
pattern. Let's say we wanted to fetch the latest stream offset on every status 
call. If every time when the status check happens, there's some new events 
available on the stream that have not yet been ingested/processed, then this 
status checker declares that the consumption is not caught up while indeed 
there are few messages left. That would prevent using the data in this server 
for querying which wouldn't be desirable.


-- 
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-unsubscr...@pinot.apache.org

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



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org

Reply via email to