fix: refresh loads in async client - #3779
Conversation
Signed-off-by: mikemikimike <13286568797@163.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mikemikimike The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Tick the box to add this pull request to the merge queue (same as
|
|
I checked out this PR in an isolated worktree and ran the complete async client operations test module with the PR source forced on Both new regression cases pass:
I also verified that the progress-only handler is not used by either path. I did not find a correctness issue in the changed scope. |
Closes #3772
AsyncMilvusClient.refresh_load()currently delegates to the low-level progress query instead of requesting a load refresh. As a result, async callers andoptimize_collection()can return without reloading refreshed segments.This change reuses the existing async load paths: collections call
load_collection(..., _refresh=True), while partition refreshes callload_partitions(..., _refresh=True). Regression tests verify both routes and ensure the progress-only handler is not used.Validation: async client unit tests passed (81); Ruff format/check and
git diff --checkpassed. A targeted mypy run is blocked by existing missing grpc/milvus-lite stubs and generated protobuf stub syntax errors.This contribution was prepared with assistance from an AI agent.