[Internal] Thin Client Integration: Fixes location cache update for thinclient read and write locations.#5152
Merged
kirankumarkolli merged 5 commits intomasterfrom May 1, 2025
Conversation
kirankumarkolli
approved these changes
Apr 30, 2025
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.
Pull Request Template
Description
The location cache overrides the thinclient read and write endpoint value with default endpoint value after GetDatabaseAccount refresh call is made. This leads to 410 error getting generated on create and read item requests via thinclient mode due to wrong endpoint value.
As part of the fix, updating the location cache code logic for setting thinclient read and write endpoint location.
Type of change
Please delete options that are not relevant.
Closing issues
To automatically close an issue: closes #5151