Fix Indexing of lastUpdated for Deleted Resources #469
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.
When deleting a resource, a resource content with type and id only was
stored and indexed. However, because the lastUpdated timestamp is not
part of the resource content, it was associated to the resource content
before indexing. So the lastUpdate timestamp was indexed even for the
deleted version of a resource, so that a search for _lastUpdated found
that version and returned it as match in results.
This patch completely omits storing and indexing of deleted resource
contents and uses the hash consisting of all zero bytes for the
resource handle. Pulling such a deleted resource handle will return a
resource content consisting of type and id only immediately.