sijie commented on issue #6847: URL: https://github.com/apache/pulsar/issues/6847#issuecomment-628764737
@gfredericks sorry for the late response. I think the contract is the reader should read every message that is available in the storage. The `consumer_backlog_eviction` and `TTL` are the policies attached for quota management for topics in a namespace. These settings are how brokers manage the storage for topics that should be independent of how readers and consumers receiving messages. In other words, if a reader to read messages, people should make sure those storage quota policies don't apply to the topics. With that being said, if people do configure those storage quota settings to the topics and a reader is reading those topics, the broker should detect that the data is cleaned up due to its storage quota policy and throw an exception to the client without silently dropping the messages. So +1 to your last comment that we need to throw an exception to the clients. A pull request would work for adding this fix. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
