MB-65473: Adapt to change in bleve_index_api interface for VectorReader

[abhinavdangeti]

Aligns with:

• MB-65473: Refactor and Optimize Pre-Filtered Vector Search bleve_index_api#63 + MB-65473: Extend VectorReader interface to get the EligibleDocumentSelector bleve_index_api#66
• MB-65473: Refactor and Optimize Pre-Filtered Vector Search bleve#2169

[abhinavdangeti]

@CascadingRadium can you confirm that segIdx in SegmentEligibleDocs(..) in the single document index is zero?

[coveralls]

Pull Request Test Coverage Report for Build 14201074977

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 85.464%

---

Totals
Change from base Build 13844035984:	0.0%
Covered Lines:	488
Relevant Lines:	571

---

💛 - Coveralls

[CascadingRadium]

provided that a sear user is configuring the VectorReader usage appropriately (sear does not have the concept of bleve/zap) then this logic is correct. In the bleve side of things, if there is only 1 document, there will be only 1 segment to search, and selector.SegmentEligibleDocs(0) can either have 1 value (if eligible) or be nil/empty which is handled here using the NewVectorFieldReaderEmpty

[abhinavdangeti]

v0.3.3