fix regex resolver match 0 or 1 tenant bug#7424
Open
SungJin1212 wants to merge 1 commit intocortexproject:masterfrom
Open
fix regex resolver match 0 or 1 tenant bug#7424SungJin1212 wants to merge 1 commit intocortexproject:masterfrom
SungJin1212 wants to merge 1 commit intocortexproject:masterfrom
Conversation
Signed-off-by: SungJin1212 <tjdwls1201@gmail.com>
CharlieTLe
approved these changes
Apr 15, 2026
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
2 participants
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.
Fix
unsupported charactererror whentenant-federation.regex-matcher-enabledis enabled and the input regex matches 0 or 1 existing tenant.Ingester Side (Use Single Resolver): The raw regex was propagated to ingesters via context instead of the resolved tenant ID, causing validation errors for patterns containing characters unsupported in tenant IDs (e.g.
+).Store Gateway Side: The tenantID is passed by the querier (Use Resolve Resolver), so the query results are partially returned only by the Store Gateway side in #7413(Issue 2).
Which issue(s) this PR fixes:
Fixes #7413
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]