Github user joefk commented on the issue:
https://github.com/apache/incubator-pulsar/issues/523
If there needs to be a hard limit (for 100% assurance), the application can
enforce that itself without any changes in the system (Pulsar).
My perspective is from what I think as the origin of this ask: If there
is a system(Pulsar) limit, and if the system can honor a "violating" request
by optimizing the request, it should. Agreed that sometimes the system will
not always succeed in this, but it should try. That could reduce user impact
by reducing the number of violations, and some use-cases might prefer that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
