Skip to content

test: add positive case for decay reranker on add_collection_field nullable input#49055

Open
NicoYuan1986 wants to merge 1 commit intomilvus-io:masterfrom
NicoYuan1986:test/add-field-decay-reranker-positive
Open

test: add positive case for decay reranker on add_collection_field nullable input#49055
NicoYuan1986 wants to merge 1 commit intomilvus-io:masterfrom
NicoYuan1986:test/add-field-decay-reranker-positive

Conversation

@NicoYuan1986
Copy link
Copy Markdown
Contributor

@NicoYuan1986 NicoYuan1986 commented Apr 15, 2026

Summary

PR #47919 (Arrow-based function chain pipeline) removed the Go-side Function input field cannot be nullable validation in internal/util/function/rerank/rerank_base.go. As a result, a nullable field added via add_collection_field is now an accepted input for a decay reranker.

This PR replaces the previous negative case test_milvus_client_add_field_with_reranker_unsupported (which expected the now-removed validation error) with a positive case test_milvus_client_add_field_used_as_decay_reranker_input, covering the combination add_collection_field(nullable=True) + decay reranker on the new field and asserting that search succeeds.

@sre-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: NicoYuan1986
To complete the pull request process, please assign czs007 after the PR has been reviewed.
You can assign the PR to them by writing /assign @czs007 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

@sre-ci-robot sre-ci-robot added area/test size/M Denotes a PR that changes 30-99 lines. sig/testing labels Apr 15, 2026
@mergify mergify bot added dco-passed DCO check passed. kind/test labels Apr 15, 2026
@sre-ci-robot
Copy link
Copy Markdown
Contributor

[ci-v2-notice]
Notice: New ci-v2 system is enabled for this PR.

To rerun ci-v2 checks, comment with:

  • /ci-rerun-code-check // for ci-v2/code-check
  • /ci-rerun-build // for ci-v2/build
  • /ci-rerun-build-all // for ci-v2/build-all (multi-arch builds)
  • /ci-rerun-buildenv // for ci-v2/build-env (build milvus-env builder images)
  • /ci-rerun-ut-integration // for ci-v2/ut-integration, will rerun ci-v2/build
  • /ci-rerun-ut-go // for ci-v2/ut-go, will rerun ci-v2/build
  • /ci-rerun-ut-cpp // for ci-v2/ut-cpp
  • /ci-rerun-ut // for all ci-v2/ut-integration, ci-v2/ut-go, ci-v2/ut-cpp, will rerun ci-v2/build
  • /ci-rerun-e2e-default // for ci-v2/e2e-default
  • /ci-rerun-e2e-amd // for ci-v2/e2e-amd (e2e pool dispatcher)
  • /ci-rerun-build-ut-cov // for ci-v2/build-ut-cov (build + unit tests in one pipeline)
  • /ci-rerun-gosdk // for ci-v2/go-sdk (Go SDK E2E tests, ARM)

If you have any questions or requests, please contact @zhikunyao.

PR milvus-io#47919 (Arrow-based function chain pipeline) removed the Go-side
"Function input field cannot be nullable" validation, so the previous
negative case test_milvus_client_add_field_with_reranker_unsupported is
no longer valid: a nullable field added via add_collection_field is now
an accepted decay reranker input.

Replace it with a positive case that performs search with a decay
reranker referencing the newly added nullable field and asserts the
search succeeds.

Signed-off-by: nico <cheng.yuan@zilliz.com>
@NicoYuan1986 NicoYuan1986 force-pushed the test/add-field-decay-reranker-positive branch from 370ad21 to ea1fbbb Compare April 15, 2026 09:09
@sre-ci-robot sre-ci-robot added size/L Denotes a PR that changes 100-499 lines. and removed size/M Denotes a PR that changes 30-99 lines. labels Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/test dco-passed DCO check passed. kind/test sig/testing size/L Denotes a PR that changes 100-499 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants