(feat): add user defined topic dimension consumer limiter #895
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #895 +/- ##
==========================================
- Coverage 23.81% 23.73% -0.09%
==========================================
Files 52 52
Lines 7105 7129 +24
==========================================
Hits 1692 1692
- Misses 5187 5211 +24
Partials 226 226
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
superhx
force-pushed
the
feat_consumer_limiter
branch
from
9ef0fd5
to
241b453
Compare
ShannonDing
requested review from
cserwen,
francisoliverlee,
maixiaohai,
xujianhai666,
yuz10 and
zongtanghu
ShannonDing
approved these changes
Aug 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
Add user defined consume rate limiter which is topic dimension. The user could use self defined Limiter 'block' consume to controller topic consume rate based on TPS / Concurrent / Load or any other condition.
Brief changelog
#896