Repository navigation
fix(indexing): lancedb migration guards + E10 negative result - #36
Merged
Merged
Conversation
added 4 commits
September 19, 2026 10:12
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
What
Critical production fix for silent lancedb schema loss + a recorded negative experiment.
fix(indexing): guard lancedb migration + recreate against silent schema loss
db_managerimportedIndexerTableMixinclass methods as module-level functions -> ImportError -> column migration ran silently nowhere (prod incident).db_writer.is_table_missingtreatedfield 'X' does not exist in table schema(schema-mismatch) as missing table -> full rebuild (drop + ~13 min re-embed) instead of soft migration.pa.fieldfromself.schema; recreate only on real table absence ("in table schema" excluded). +200 lines of regression tests (tests/test_lancedb_recreate.py, 12 passed).refactor(settings): restore MAX_RERANKER_INPUT default 30 behind env toggle — behavior identical to HEAD; pool re-test possible via env.
chore(experiments): keep
scripts/e2e_quality_search.py(quality harness) +experiments/search_quality/E10_full_text_embed.py(rerunnable artifact).docs: migration incident + E10 negative result (EXPERIMENTS_LOG / AGENT_DIARY / KNOWN_ISSUES / portfolio exp-43).
Experiment E10 (REFUTED)
Hypothesis: full-text chunk embedding + e5 query:/passage: prefixes (llama.cpp branch) + reranker pool 50 lift search hit. Clean rebuild: 599 files / 9514 chunks in 799.9s. Result vs author baseline — within N=10 noise: fast hit@1=0%/- hit@5=50%/50%; quality hit@1=20%(baseline 30%) hit@5=40%(baseline 30%). Code reverted to HEAD. Pure-vector plateau reconfirmed; next: AST/Graph-hybrid re-ranking.
Verification
lab.test.ts+evidence-eval.test.ts): 26/26 passed (exp-43 EN/RU congruent).