Skip to content

set AP query for tables with large row size and vector indexes #22705

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

Open
iamlinjunhong wants to merge 1 commit into
base: v2.2.2-hotfix
Choose a base branch
from

set AP query for tables with large row size and vector indexes

0991193
Select commit
Loading
Failed to load commit list.
Open

set AP query for tables with large row size and vector indexes #22705

set AP query for tables with large row size and vector indexes
0991193
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 29, 2025 in 0s

1 rule matches and 8 potential rules

✅ Rule: Auto Request Reviewer For Non Main Branch (request_reviews)

  • base!=main

Rule: Auto update branch (update)

  • #commits-behind > 0 [📌 update requirement]
  • created-at>=00:10 ago
  • -closed [📌 update requirement]
  • -conflict [📌 update requirement]
  • queue-position = -1 [📌 update requirement]

Rule: label for Bug (label)

  • body~=(?im)- \[x\] BUG

Rule: label for Feature (label)

  • body~=(?im)- \[x\] Feature

Rule: label for Improvement (label)

  • body~=(?im)- \[x\] Improvement

Rule: label for Documentation (label)

  • body~=(?im)- \[x\] Documentation

Rule: label for Test and CI (label)

  • body~=(?im)- \[x\] Test and CI

Rule: label for Code Refactoring (label)

  • body~=(?im)- \[x\] Code Refactoring

Rule: label for API-change (label)

  • body~=(?im)- \[x\] API-change
💖  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: Automatic queue on approval for main (queue)

  • base=main
  • #changes-requested-reviews-by<=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label!=do-not-merge/wip
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 queue requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue main]

Rule: Automatic queue on approval for release-3.0 (queue)

  • approved-reviews-by=XuPeng-SH
  • base=3.0-dev
  • #changes-requested-reviews-by<=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label!=do-not-merge/wip
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 queue requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue release-3.0]

Rule: Automatic queue on approval for release-2.2 (queue)

  • approved-reviews-by=XuPeng-SH
  • base=2.2-dev
  • #changes-requested-reviews-by<=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label!=do-not-merge/wip
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 queue requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue release-2.2]

Rule: Automatic queue on approval for release-2.1 (queue)

  • approved-reviews-by=XuPeng-SH
  • base=2.1-dev
  • #changes-requested-reviews-by<=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label!=do-not-merge/wip
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 queue requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue release-2.1]
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