Skip to content

enhance: revert the bulk import idempotency key fields - #657

Open
bigsheeper wants to merge 1 commit into
milvus-io:masterfrom
bigsheeper:revert/bulk-import-idempotency-key
Open

enhance: revert the bulk import idempotency key fields#657
bigsheeper wants to merge 1 commit into
milvus-io:masterfrom
bigsheeper:revert/bulk-import-idempotency-key

Conversation

@bigsheeper

Copy link
Copy Markdown
Contributor

issue: milvus-io/milvus#50954

What

Reverts the idempotency_key fields added in #633:

  • ImportRequest.idempotency_key = 9 (proto/milvus.proto)
  • ImportMsg.idempotency_key = 10 (proto/msg.proto)

Why

The implementation those fields were added for landed on a different design. milvus-io/milvus#52544 makes broadcast generically idempotent rather than making BulkImport idempotent: the client key travels as gRPC metadata (idempotency-key) / the REST Idempotency-Key header, is copied onto coordinator RPCs by a shared unary client interceptor, and reaches the broadcaster as a message property. No request proto carries it, and no message body field is read.

Both fields are therefore unused. Neither is referenced by any Go code in milvus master today, and milvus pins v3.0.0-20260806081414-16b288837fbd — the commit immediately preceding #633 — so the fields have never been consumed.

Field numbers

9 and 10 are released rather than reserved. git tag --contains 9810b92 is empty: no tagged release of this repo ever exposed them, so no consumer can hold a wire encoding that uses them. Say the word if you would rather reserve them anyway and I will add the reserved entries.

Changes

  • Remove the two fields from proto/milvus.proto and proto/msg.proto.
  • Regenerate go-api/milvuspb/milvus.pb.go and go-api/msgpb/msg.pb.go.

Verification

  • Regenerated with the toolchain the checked-in files were built with — protoc 3.21.4, protoc-gen-go v1.33.0, protoc-gen-go-grpc v1.3.0 — using the exact scripts/proto_gen_go.sh invocations. Control run first: regenerating at origin/master with no source change produced a byte-identical tree, so the diff here is the field removal and nothing else.
  • The non-rawDesc portion of the generated diff is exactly the two struct fields and their two getters; the rest is the descriptor byte array reflowing.
  • go build ./... and go vet ./milvuspb/... ./msgpb/... clean in go-api/.

🤖 Generated with Claude Code

@sre-ci-robot
sre-ci-robot requested review from congqixia and yhmo August 21, 2026 04:03
@sre-ci-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bigsheeper
To complete the pull request process, please assign tedxu after the PR has been reviewed.
You can assign the PR to them by writing /assign @tedxu in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mergify mergify Bot added dco-passed DCO check passed. ci-passed labels Aug 21, 2026
@mergify

mergify Bot commented Aug 21, 2026

Copy link
Copy Markdown

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@bigsheeper
bigsheeper force-pushed the revert/bulk-import-idempotency-key branch from 11c7f51 to 2e99f3b Compare August 25, 2026 06:36
@mergify mergify Bot added ci-passed and removed ci-passed labels Aug 25, 2026
Reverts the two fields added in milvus-io#633. The implementation that needed them
(milvus-io/milvus#52544) carries the client key in gRPC metadata and a broadcast
message property instead, so no request proto is involved and both fields are
unused.

Neither field appears in a tagged release, and milvus pins the commit that
precedes milvus-io#633, so field numbers 9 and 10 are released back rather than reserved.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
@bigsheeper
bigsheeper force-pushed the revert/bulk-import-idempotency-key branch from 2e99f3b to d960102 Compare August 27, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants