Summary
The search and query iterator implementations currently live in the ORM layer. They should be moved to MilvusClient so that users of the client API get first-class iterator support without going through ORM.
Motivation
MilvusClient is the recommended API surface. Keeping iterators in ORM forces users to either use ORM directly or rely on thin wrappers that don't fully leverage the client's connection management and performance improvements.
Scope
- Move
SearchIterator and QueryIterator logic to MilvusClient
- Deprecate (or remove) the ORM-based iterator entry points
- Ensure backward compatibility during transition
Summary
The search and query iterator implementations currently live in the ORM layer. They should be moved to
MilvusClientso that users of the client API get first-class iterator support without going through ORM.Motivation
MilvusClientis the recommended API surface. Keeping iterators in ORM forces users to either use ORM directly or rely on thin wrappers that don't fully leverage the client's connection management and performance improvements.Scope
SearchIteratorandQueryIteratorlogic toMilvusClient