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
|
|
@ -613,7 +613,7 @@ vfsFiles.forEach(f => {
|
|||
})
|
||||
|
||||
// 3. VFS FILTERING IN KNOWLEDGE QUERIES
|
||||
console.log('\n🔍 Understanding VFS filtering (v4.4.0)...\n')
|
||||
console.log('\n🔍 Understanding VFS filtering...\n')
|
||||
|
||||
// Create some knowledge entities
|
||||
const conceptId = await brain.add({
|
||||
|
|
@ -758,7 +758,7 @@ await brain.close()
|
|||
|
||||
### Key Concepts
|
||||
|
||||
#### 1. **VFS Filtering Architecture (v4.4.0)**
|
||||
#### 1. **VFS Filtering Architecture**
|
||||
|
||||
```typescript
|
||||
// 🎯 DEFAULT BEHAVIOR: Clean Separation
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue