Speed up search iterators via using iterator directly rather than calling range search and maintain radius and range_filter on the SDK, which adds complexity to SDK implementations.
Why is this needed?
E2E Search Iterator becomes fundamental to workflows like client-side post filtering and others.
Replace the underlying Range Search Calls with Knowhere iterator Next() calls. For each SDK Next() call, construct Knowhere iterators at segment level and calling Next() on them. Do NOT hold iterators at this stage.
Is there an existing issue for this?
What would you like to be added?
Speed up search iterators via using iterator directly rather than calling range search and maintain
radius
andrange_filter
on the SDK, which adds complexity to SDK implementations.Why is this needed?
E2E Search Iterator becomes fundamental to workflows like client-side post filtering and others.
Anything else?
No response