br: compatible with and add integration test for partial index

[Leavrth]

What problem does this PR solve?

Issue Number: ref #62664

Problem Summary:
To be compatible with partial index for repairing ingest index after log restore

What changed and how does it work?

recognize the IndexInfo.ConditionExprString

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @Leavrth. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[YangKeao]

LGTM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.2628%. Comparing base (8c27816) to head (46d88aa).
⚠️ Report is 28 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #64434        +/-   ##
================================================
+ Coverage   72.6827%   75.2628%   +2.5801%     
================================================
  Files          1865       1867         +2     
  Lines        506065     513443      +7378     
================================================
+ Hits         367822     386432     +18610     
+ Misses       115852     103964     -11888     
- Partials      22391      23047       +656     

Flag	Coverage Δ
integration	45.8371% <100.0000%> (?)
unit	73.1189% <0.0000%> (+0.8638%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.8700% <ø> (ø)
parser	∅ <ø> (∅)
br	63.6156% <100.0000%> (+17.4051%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, YangKeao

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• br/OWNERS [3pointer]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-11-12 06:20:08.284925317 +0000 UTC m=+855857.727955196: ☑️ agreed by YangKeao.
• 2025-11-18 04:07:37.388822839 +0000 UTC m=+1366306.831852717: ☑️ agreed by 3pointer.

[BornChanger]

/retest

[tiprow]

@BornChanger: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[YangKeao]

/cherry-pick release-8.5-20260116-v8.5.5

[ti-chi-bot]

@YangKeao: new pull request created to branch release-8.5-20260116-v8.5.5: #65917.

Details

In response to this:

/cherry-pick release-8.5-20260116-v8.5.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.