ARTEMIS-5953 Allow address federation bindings to group under a wildcard#6296
Open
tabish121 wants to merge 1 commit intoapache:mainfrom
Open
ARTEMIS-5953 Allow address federation bindings to group under a wildcard#6296tabish121 wants to merge 1 commit intoapache:mainfrom
tabish121 wants to merge 1 commit intoapache:mainfrom
Conversation
Add configuration that enables the address federation policy matches to define if a remote wildcard address will be used to host the address receiver bindings for the matching addresses if the match value is itself a wildcard. This can be useful if federating large numbers of addresses that have low traffic as it reduces the number of addresses that need to exist on the remote federation target at the expense of higher CPU load on the target in order to route messages to the appropriate wildcard bindings for the matched addresses. The default value will be `false` and the federation receiver address bindings will be attached to the matching addresses on the remote as they always have. When enabled the remote broker must have wildcard routing enabled for this feature to work correctly.
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.
Add configuration that enables the address federation policy matches to define if a remote wildcard address will be used to host the address receiver bindings for the matching addresses if the match value is itself a wildcard. This can be useful if federating large numbers of addresses that have low traffic as it reduces the number of addresses that need to exist on the remote federation target at the expense of higher CPU load on the target in order to route messages to the appropriate wildcard bindings for the matched addresses. The default value will be
falseand the federation receiver address bindings will be attached to the matching addresses on the remote as they always have. When enabled the remote broker must have wildcard routing enabled for this feature to work correctly.