Scope & Purpose

• Fix tests
• Avoid multiple materializations, once in RocksDBIndex iterator and one after EnumeraterNearVectorNode in MaterializeNode Move evaluation in callback

Introduces filtering to the vector index. This way, we will push the filtering expression to the vector index iterator and evaluate it there. A continuation of this would be an investigation into whether the batching of documents would be beneficial, and if so, implementing it.
Now queries like this should work, and the FilterNode will be merged with the EnumerateNearVectorIndexNode:

FOR d IN col
FILTER d.val > 3
LET dist = APPROX_NEAR_L2(d.vector, @q)
SORT dist LIMIT 3 RETURN d

This implementation still does not support storedValues usage and compound indexes.

• 💩 Bugfix
• 🍕 New feature
• 🔥 Performance improvement
• 🔨 Refactoring/simplification

Checklist

• Tests
  • Regression tests
  • C++ Unit tests
  • integration tests
  • resilience tests
• 📖 CHANGELOG entry made
• 📚 documentation written (release notes, API changes, ...)
• Backports
  • Backport for 3.12.0: (Please link PR)
  • Backport for 3.11: (Please link PR)
  • Backport for 3.10: (Please link PR)

Related Information

(Please reference tickets / specification / other PRs etc)

• Docs PR:
• Enterprise PR:
• GitHub issue / Jira ticket:
• Design document: