Correct what the index-backed read path actually guarantees

DocsInitializerService
Shipped
14 Agosti 2026, 02:57 UTC
Author
Kamo
Commit
c0d45fc

The previous comment claimed the read path "refuses to serve any folder it cannot prove it agrees with the server about — so a row that is wrong here is a row that path will not use." That is not true, and it was the reasoning that made a FALSE backfill look free. The check proves the index holds the same messages as the server. Flags change without moving a message count or a UIDNEXT, and nothing re-indexes a message when they do, so a stale flag is not something that check can see. The migration is unchanged and correct; only the justification was wrong. Ran against Yugabyte 2026-08-13: column present, boolean, default false, no nulls remaining.

All changes

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei