You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Right now, there is no way to limit the number of pull queries that can be run against a particular ksqlDB server. As this is an early stage feature with many non-functional unknowns around performance, cost, etc., it would be good to enable optional rate limiting so that users can try the feature without risking negative unknowns.
Describe the solution you'd like
A configurable global rate limit across all materialized state stores which throttles request rate would be a great starting point.
Describe alternatives you've considered
More fancy multi-note limits, bandwidth limits, etc., are not necessary at this point.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Right now, there is no way to limit the number of pull queries that can be run against a particular ksqlDB server. As this is an early stage feature with many non-functional unknowns around performance, cost, etc., it would be good to enable optional rate limiting so that users can try the feature without risking negative unknowns.
Describe the solution you'd like
A configurable global rate limit across all materialized state stores which throttles request rate would be a great starting point.
Describe alternatives you've considered
More fancy multi-note limits, bandwidth limits, etc., are not necessary at this point.
The text was updated successfully, but these errors were encountered: