Add configurable limit for topic-to-external-resource mappings #894
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.
Summary
This PR introduces a configurable hard limit for the number of topic-to-external-resource mappings.
Changes Made
New Configuration Parameter
max.external.resource.mappings
Validation Logic
getTopicToExternalResourceMap()
method to enforce the mapping limitConfigException
with descriptive error message when limit is exceededTest Coverage
Added comprehensive test cases in
ValidatorTest.java
:testValidMappingWithinLimit()
- Verifies mappings within limit work correctlytestInvalidTooManyMappings()
- Tests custom limit enforcementtestDefaultMappingLimit()
- Validates default limit of 15 mappingsConfiguration Usage
Users can now configure the connector with a custom limit:
Error Handling
When the limit is exceeded, users receive a clear error message:
Backward Compatibility
Testing