Add a query result limit to regex matcher #6845
Open
+35
−14
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.
This PR implements a
tenant-federation.max-tenant
flag logic when thetenant-federation.regex-matcher-enabled
flag is enabled.Since the QFE uses a
regex validator
, which validates input regex and passes it to the Query scheduler or Querier, the QFE handler cannot validate the max tenant limit.Instead of emitting an error when # of matched tenants over the
tenant-federation.max-tenant
, I adjusted # of tenants to query because # of matched tenants is unexpected if the user uses a regex likeuser-+
.Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]