kafka: preserve native explicit-quota window limits - #590
Draft
bringhurst wants to merge 1 commit into
Draft
bringhurst wants to merge 1 commit into
bringhurst wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The static-quota addition treated any limit at or above Long.MaxValue as absent, including an explicit dynamic quota with the bridge feature disabled. Restore the original callback calculation and use the gated static default only when the callback returns no value. The new native-path regression fails before the repair (finite 9.22e19 expected, Double.MaxValue returned). The complete ClientQuotaManagerTest, QuotaFactoryTest and RequestQuotaTest suites pass afterward, including fallback restoration after removing an override. No new feature or default is enabled.