Allow partial data in tenant-federation#7232
Open
SungJin1212 wants to merge 4 commits intocortexproject:masterfrom
Open
Allow partial data in tenant-federation#7232SungJin1212 wants to merge 4 commits intocortexproject:masterfrom
SungJin1212 wants to merge 4 commits intocortexproject:masterfrom
Conversation
Signed-off-by: SungJin1212 <tjdwls1201@gmail.com>
SungJin1212
changed the title
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.
This PR introduces experimental flag
-tenant-federation.allow-partial-datafor partial responses when using Tenant Federation.Currently, when querying multiple tenants via federation, a failure in a single tenant causes the entire query to fail. With this change, users can opt-in to a mode where errors from individual tenants are treated as warnings, allowing partial results from successful tenants to be returned.
This is particularly useful when using the regex resolver (e.g., X-Scope-OrgID: user-.*). When dynamically matching a large number of tenants, a single failing tenant will no longer block the entire query result.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]