NODE-8012Backlog

[Mastra] Define how MongoDBVector refreshes cached index state after external changes

h2. TL;DR Each {{MongoDBVector}} instance caches where an index lives and which fields its search index can filter on. It doesn't notice when another process or a database admin changes them, so it keeps using stale values until it restarts. Choose and document a refresh strategy. h2. Context {{MongoDBVector}} keeps three in-process caches: * {{indexTargets}}: the logical index name's collection, search index names, and write policy, read from the registry. * {{declaredFilterPaths}}: the fields

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue
ABX
Labels
Tags and classification
node-internal