[Bugfix] Throw DocumentNotFoundError if index doesnt exist when looking for doc by id #2916
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.
Changes
NotFoundError
->DocumentNotFoundError
(consistent with the rest of framework)The index refresh operation should be wrapped in a
try/catch
block. Otherwise, if we’re searching for a document in an index that doesn’t exist yet, it throws aNotFoundError
instead of aDocumentNotFoundError
. In my opinion, if the document doesn’t exist because the underlying index is missing, we should still return aDocumentNotFoundError
. This also simplifies the caller logic, as we only need to handle a single exception type.Update logs from
critical
toerror
. In my opinion, thecritical
log level should be reserved for cases that cause the entire framework to fail. In most, if not all, of these cases, we either retry or have some graceful handling, so it’s appropriate to log them at just theerror
level.