table: Add option SkipWriteUntouchedIndices for Table.UpdateRecord

[lcwangchao]

What problem does this PR solve?

Issue Number: ref #54397

What changed and how does it work?

table.SkipWriteUntouchedIndices is introduced as a new option for Table.UpdateRecord. It is used to decouple the code of UpdateRecord and the executor logic. It makes the code more clear and easier to read.

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 @lcwangchao. 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.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.4029%. Comparing base (1985662) to head (09746b1).
Report is 4 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55192        +/-   ##
================================================
- Coverage   74.8010%   73.4029%   -1.3982%     
================================================
  Files          1570       1570                
  Lines        364690     439898     +75208     
================================================
+ Hits         272792     322898     +50106     
- Misses        72131      97058     +24927     
- Partials      19767      19942       +175     

Flag	Coverage Δ
integration	25.2695% <100.0000%> (?)
unit	71.7194% <100.0000%> (-1.9598%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (-2.2327%)	⬇️
parser	∅ <ø> (∅)
br	46.0991% <ø> (-1.5754%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crazycs520, tangenta

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [crazycs520,tangenta]
• pkg/table/OWNERS [tangenta]

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:

• 2024-08-06 06:19:26.477480344 +0000 UTC m=+332896.344579430: ☑️ agreed by crazycs520.
• 2024-08-06 06:22:37.2037527 +0000 UTC m=+333087.070851788: ☑️ agreed by tangenta.

[lcwangchao]

/retest

[tiprow]

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

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.