Skip to content

fix: Handle empty FieldsData in reduce/rerank for requery scenario #44917

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 21, 2025

fix: Handle empty FieldsData in reduce/rerank for requery scenario

7bade09
Select commit
Loading
Failed to load commit list.
Merged

fix: Handle empty FieldsData in reduce/rerank for requery scenario #44917

fix: Handle empty FieldsData in reduce/rerank for requery scenario
7bade09
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 21, 2025 in 0s

4 rules match and 24 potential rules

⚠️ The pull request has been merged by @sre-ci-robot

Rule: Add needs-dco label when DCO check failed (comment, label)

  • -status-success=DCO
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

✅ Rule: Add dco-passed label when DCO check passed (label)

  • status-success=DCO
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

✅ Rule: Test passed for code changed on master (label)

  • base=master
  • status-success=Code Checker MacOS 13
  • any of:
    • status-success=ci-v2/build
    • status-success=Build and test AMD64 Ubuntu 22.04
  • any of:
    • status-success=go-sdk
    • status-success=ci-v2/go-sdk
    • status-success=milvus-sdk-go
  • any of:
    • status-success=ci-v2/ut-cpp
    • status-success=UT for Cpp
    • status-success=cpp-unit-test
  • any of:
    • status-success=ci-v2/ut-go
    • status-success=UT for Go
    • status-success=go-unit-test
  • any of:
    • status-success=ci-v2/integration-test
    • status-success=Integration Test
    • status-success=integration-test
  • any of:
    • status-success=cpu-e2e
    • status-success=ci-v2/e2e-default
  • any of:
    • status-success=ci-v2/code-check
    • status-success=Code Checker AMD64 Ubuntu 22.04

Rule: Test passed for tests changed (label)

  • -files~=^(?!tests\/python_client).+
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=cpu-e2e
    • status-success=ci-v2/e2e-default

Rule: Test passed for docs changed only (label)

  • -files~=^(?!.*\.(md)).*$
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Test passed for non rust go or c++ code changed (label)

  • -files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=cpu-e2e
    • status-success=ci-v2/e2e-default

Rule: Test passed for go unittest code changed-master (label)

  • -files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
  • status-success=Code Checker MacOS 13
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=ci-v2/build
    • status-success=Build and test AMD64 Ubuntu 22.04
  • any of:
    • status-success=ci-v2/code-check
    • status-success=Code Checker AMD64 Ubuntu 22.04
  • any of:
    • status-success=ci-v2/ut-go
    • status-success=UT for Go
    • status-success=go-unit-test

Rule: Test passed for mergify changed (label)

  • -files~=^(?!\.github\/mergify\.yml).*$
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Test passed for title skip e2e when no source code changed (label)

  • -files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • label=kind/enhancement
  • title~=\[skip e2e\]
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Test passed for skip e2e when source code changed (label)

  • title~=\[skip e2e\]
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • status-success=Code Checker MacOS 13
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=ci-v2/build
    • status-success=Build and test AMD64 Ubuntu 22.04
  • any of:
    • status-success=ci-v2/ut-cpp
    • status-success=UT for Cpp
    • status-success=cpp-unit-test
  • any of:
    • status-success=ci-v2/ut-go
    • status-success=UT for Go
    • status-success=go-unit-test
  • any of:
    • status-success=ci-v2/integration-test
    • status-success=Integration Test
    • status-success=integration-test
  • any of:
    • status-success=ci-v2/code-check
    • status-success=Code Checker AMD64 Ubuntu 22.04

Rule: Remove ci-passed when any CI system fails during migration (label)

  • any of:
    • all of:
      • any of:
        • status-failure = Build and test AMD64 Ubuntu 22.04
        • status-failure = ci-v2/build
      • not:
        • any of:
          • status-success = ci-v2/build
          • status-success = Build and test AMD64 Ubuntu 22.04
    • all of:
      • any of:
        • status-failure = UT for Go
        • status-failure = ci-v2/ut-go
      • not:
        • any of:
          • status-success = ci-v2/ut-go
          • status-success = UT for Go
    • all of:
      • any of:
        • status-failure = Integration Test
        • status-failure = ci-v2/integration-test
      • not:
        • any of:
          • status-success = ci-v2/integration-test
          • status-success = Integration Test
    • all of:
      • any of:
        • status-failure = ci-v2/ut-cpp
        • status-failure = cpp-unit-test
      • not:
        • any of:
          • status-success = ci-v2/ut-cpp
          • status-success = cpp-unit-test
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
    • all of:
      • any of:
        • status-failure = Code Checker AMD64 Ubuntu 22.04
        • status-failure = ci-v2/code-check
      • not:
        • any of:
          • status-success = ci-v2/code-check
          • status-success = Code Checker AMD64 Ubuntu 22.04
    • all of:
      • any of:
        • status-failure = ci-v2/e2e-default
        • status-failure = cpu-e2e
      • not:
        • any of:
          • status-success = cpu-e2e
          • status-success = ci-v2/e2e-default
    • all of:
      • any of:
        • status-failure = ci-v2/e2e-default
        • status-failure = cpu-e2e
      • not:
        • any of:
          • status-success = cpu-e2e
          • status-success = ci-v2/e2e-default
      • -title~=\[skip e2e\]
      • files~=^(?!(.*_test\.go|.*\.md|\.github\/mergify\.yml)).*$
    • any of:
      • status-success != Code Checker MacOS 13
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • label!=manual-pass
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Blocking PR if missing a related issue or doesn't have kind/enhancement label (comment, label)

  • all of:
    • -body~=\#[0-9]{1,6}(\s+|$)
    • -body~=https://github.com/milvus-io/milvus/issues/[0-9]{1,6}(\s+|$)
  • -label=kind/doc
  • -label=kind/test
  • -title~=\[automated\]
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • any of:
    • label=kind/bug
    • label=kind/feature
    • all of:
      • label=kind/enhancement
      • any of:
        • label=size/L
        • label=size/XL
        • label=size/XXL

✅ Rule: Dismiss block label if related issue be added into PR (label)

  • all of:
    • any of:
      • base=master
      • base~=^2(\.\d+){1,2}$
    • any of:
      • body~=\#[0-9]{1,6}(\s+|$)
      • body~=https://github.com/milvus-io/milvus/issues/[0-9]{1,6}(\s+|$)

Rule: Dismiss block label if automated create PR (label)

  • title~=\[automated\]
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add 'do-not-merge/invalid-pr-format' label for invalid PR titles (comment, label)

  • any of:
    • -title~=^(feat:|enhance:|fix:|test:|doc:|auto:|build\(deps\):|\[automated\])
    • body=^$
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Remove 'do-not-merge/invalid-pr-format' label for valid PRs (label)

  • label=do-not-merge/invalid-pr-format
  • -body=^$
  • title~=^(feat:|enhance:|fix:|test:|doc:|auto:|build\(deps\):|\[automated\])
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when cpu-e2e job failed (comment)

  • check-failure=cpu-e2e
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when go-sdk check failed (comment)

  • check-failure=go-sdk
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when cpp-unit-test check failed (comment)

  • check-failure=cpp-unit-test
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when go-unit-test check failed (comment)

  • check-failure=go-unit-test
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when integration-test check failed (comment)

  • check-failure=integration-test
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when code checker or ut failed -master (comment)

  • any of:
    • check-failure=Build and test AMD64 Ubuntu 20.04
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

✅ Rule: Label bug fix PRs (label)

  • title~=^fix:
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label feature PRs (label)

  • title~=^feat:
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label enhancement PRs (label)

  • title~=^enhance:
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label test PRs (label)

  • title~=^test:
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label doc PRs (label)

  • title~=^doc:
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Assign the 'lgtm' and 'approved' labels following the successful testing of the 'Update Knowhere Commit' (label)

  • title~=Update Knowhere Commit
  • label=ci-passed
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

4 not applicable rules

Rule: Test passed for code changed on 2.* branch (label)

  • base~=^2(\.\d+){1,2}$
  • status-success=Code Checker MacOS 13
  • any of:
    • status-success=ci-v2/build
    • status-success=Build and test AMD64 Ubuntu 22.04
  • any of:
    • status-success=ci-v2/ut-cpp
    • status-success=UT for Cpp
    • status-success=cpp-unit-test
  • any of:
    • status-success=ci-v2/ut-go
    • status-success=UT for Go
    • status-success=go-unit-test
  • any of:
    • status-success=ci-v2/integration-test
    • status-success=Integration Test
    • status-success=integration-test
  • any of:
    • status-success=cpu-e2e
    • status-success=ci-v2/e2e-default
  • any of:
    • status-success=ci-v2/code-check
    • status-success=Code Checker AMD64 Ubuntu 22.04

Rule: Blocking PR if missing a related master PR or doesn't have kind/branch-feature label (comment, label)

  • base~=^2(\.\d+){1,2}$
  • -label=kind/branch-feature
  • -title~=\[automated\]
  • all of:
    • -body~=https://github.com/milvus-io/milvus/pull/[0-9]{1,6}(\s+|$)
    • -body~=pr\:\ \#[0-9]{1,6}(\s+|$)

Rule: Dismiss block label if related pr be added into PR (label)

  • base~=^2(\.\d+){1,2}$
  • any of:
    • body~=https://github.com/milvus-io/milvus/pull/[0-9]{1,6}(\s+|$)
    • body~=pr\:\ \#[0-9]{1,6}(\s+|$)
    • label=kind/branch-feature

Rule: Add comment when code checker or ut failed -2.2.* (comment)

  • base~=^2(\.\d+){1,2}$
  • any of:
    • check-failure=Build and test AMD64 Ubuntu 20.04
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

View more details on Mergify