fix: exclude __words__ keyword index from corruption detection and getStats()
The __words__ keyword index stores 50-5000 entries per entity (one per word), which inflated avg entries/entity well above the corruption threshold of 100. This caused: 1. validateConsistency() to falsely detect corruption on every startup, triggering unnecessary clearAllIndexData() + rebuild() cycles 2. getStats() to log false "Metadata index may be corrupted" warnings and report inflated totalEntries/totalIds stats Both methods now skip __words__ when counting, so stats and health checks reflect metadata fields only (noun, type, createdAt, etc.). Keyword search is unaffected since the __words__ field index itself is not modified.
This commit is contained in:
parent
32dbdcec61
commit
364360d447
128 changed files with 5637 additions and 5682 deletions
|
|
@ -122,7 +122,7 @@ export class PatternSignal {
|
|||
])
|
||||
|
||||
// Location patterns - MEDIUM PRIORITY (city/country format - requires more context)
|
||||
// v4.11.2: Lower priority to avoid matching person names with commas
|
||||
// Lower priority to avoid matching person names with commas
|
||||
this.addPatterns(NounType.Location, 0.75, [
|
||||
/\b[A-Z][a-z]+,\s*(?:Japan|China|France|Germany|Italy|Spain|Canada|Mexico|Brazil|India|Australia|Russia|UK|USA)\b/
|
||||
])
|
||||
|
|
@ -170,7 +170,7 @@ export class PatternSignal {
|
|||
// Technology patterns (Thing type)
|
||||
this.addPatterns(NounType.Thing, 0.82, [
|
||||
/\b(?:JavaScript|TypeScript|Python|Java|Go|Rust|Swift|Kotlin)\b/,
|
||||
/\bC\+\+(?!\w)/, // v4.11.2: Special handling for C++ (word boundary doesn't work with +)
|
||||
/\bC\+\+(?!\w)/, // Special handling for C++ (word boundary doesn't work with +)
|
||||
/\b(?:React|Vue|Angular|Node|Express|Django|Flask|Rails)\b/,
|
||||
/\b(?:AWS|Azure|GCP|Docker|Kubernetes|Git|GitHub|GitLab)\b/,
|
||||
/\b(?:API|SDK|CLI|IDE|framework|library|package|module)\b/i,
|
||||
|
|
|
|||
Reference in a new issue