Ignore stale look up errors #5
Merged
Conversation
This file contains 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.
This is not as useful than
ignoreCacheErrorsin maxAge, which bypass cache lookup failures and reads from the source system.StaleIfError (with ignoreCacheError) will result in a error either way - this just lets us choose which error we want to expose (?)
Relates to:
https://jira.dev.bbc.co.uk/browse/IPLAYER-31785
Simply re-throws the original error not the cache lookup error. e.g HTTP 500 (original source error) not a Redis connection error attempting to get the stale content.