Write pending queue during online indexing#4293
Open
jjezra wants to merge 31 commits into
Open
Conversation
9b7b422 to
df51931
Compare
1e62e12 to
bc84cd7
Compare
This indexing option will cause user updates to accumulate in a special queue during ongoing online indexing. The indexer will drain this queue after every transaction. This resolves 4292
5c50742 to
31a5122
Compare
jjezra
commented
Jul 6, 2026
| final byte[] bitmap = new byte[(entrySize + 7) / 8]; | ||
| if (remove) { | ||
| if (state.store.isIndexWriteOnly(state.index)) { | ||
| if (state.store.isAnyIndexWriteOnly(state.index)) { |
Contributor
Author
There was a problem hiding this comment.
Rename to isIndexAnyWriteOnly?
…allsBackToWriteOnlyBelowFormatVersion
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.
During online indexing, under certain circumstances, short indexer transactions will repeatedly cause conflicts with user transactions (while the user attempts to update the index). To avoid this, we should add a new index state: WRITE_ONLY_WITH_QUEUE. In this index state, user updates will be added to a write-pending queue, and the indexer will drain the queue.