Skip to content

docs: full-text indexes are rebuilt once after the engine upgrade - #22

Merged
elvogel merged 1 commit into
mainfrom
docs/fulltext-stale-on-upgrade
Sep 30, 2026
Merged

elvogel merged 1 commit into
mainfrom
docs/fulltext-stale-on-upgrade

Conversation

@elvogel

@elvogel elvogel commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

Documents the one-time full-text index rebuild after the database moves to engine 2.4.1 (phoenixml main 8d23b02): what the server does automatically, what embedded apps must call, and the EnableIndexing()-inside-BeginWriteAsync deadlock. Adds an Unreleased release-notes entry. Verified in source at 8d23b02.

🤖 Generated with Claude Code

https://claude.ai/code/session_019zMS2EzLV6KZG6ooYco8Uf

phoenixml main 8d23b02 pins PhoenixmlDb.XQuery/Xslt 2.4.1 and records which text analysis
built each full-text index. EnableIndexing() marks every container whose index doesn't match
as stale, so existing indexes (which carry no record) are rebuilt once. The server rebuilds
them at startup through StaleIndexRebuildService; embedded apps rebuild each container in
ContainersWithStaleIndexes(). Documents the deadlock if EnableIndexing() runs inside a
BeginWriteAsync transaction.

Facts from the db-engine session, verified at 8d23b02 in DocumentDatabaseIndexingExtensions.cs,
IndexManager.SearchFullText, StaleIndexRebuildService and Program.cs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019zMS2EzLV6KZG6ooYco8Uf
@elvogel
elvogel merged commit ff87430 into main Sep 30, 2026
2 checks passed
@elvogel
elvogel deleted the docs/fulltext-stale-on-upgrade branch September 30, 2026 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant