Fix indexer logic by refreshing doc headers before indexing #89
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 PR fixes improves indexer logic by switching the order of operations where we now refresh document(+drafts) headers before indexing the documents for search. Before this, the indexer could get into a state where it was constantly indexing and refreshing the doc headers each run because the header refreshes would cause the documents to have a new modified time.
It's not exactly a hack, but note that we now track the timestamps of when we refresh headers of all documents in a folder by putting a
refreshHeaders:
prefix in thegoogle_drive_id
column for these records in theindexer_folders
table.