Return a generic 503 message when the metastore fails during authentication - #5363
Merged
Merged
Conversation
adutra
approved these changes
Aug 24, 2026
adutra
enabled auto-merge (squash)
August 24, 2026 15:16
ayushtkn
approved these changes
Aug 24, 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
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.
Follow-up to #5247, as agreed there: a client that is not yet authenticated should not learn which metastore lookup failed. The three 503s raised during authentication returned
Unable to fetch principal entity,Unable to fetch principal grantsandUnable to fetch securable entity; all three now return a fixedService unavailable.The suggestion there was to log the detail against a UUID handed back to the client. Nothing new has to be minted: the response already carries the request id as
X-Request-ID, and the default log format prints the same id asrequestId. That is the route #4406 took for the 403 path.The three
DefaultAuthenticatorTestmetastore-failure tests now assert the response message.Checklist
CHANGELOG.md(if needed)site/content/in-dev/unreleased(if needed)