*: enable infoschema v2 by default

[tiancaiamao]

What problem does this PR solve?

Issue Number: ref #50959

Problem Summary:

Before we make this change GA, we need to make sure it is stable enough.

What changed and how does it work?

On master branch, we would make it enabled by default, and run the whole period during v8.3 ~ v8.4 / v8.5
And if it's stable enough, we'll announce GA in v8.5 (LTS version)

This change would not be in v8.3, just for the master branch.

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.

Once we run infoschema v2 by default, all the tests cover it.

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 @tiancaiamao. 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 75.7356%. Comparing base (4764397) to head (55ef6a9).
Report is 26 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55229        +/-   ##
================================================
+ Coverage   74.8397%   75.7356%   +0.8959%     
================================================
  Files          1575       1578         +3     
  Lines        365139     447571     +82432     
================================================
+ Hits         273269     338971     +65702     
- Misses        72116      88636     +16520     
- Partials      19754      19964       +210     

Flag	Coverage Δ
integration	50.7287% <ø> (?)
unit	72.9248% <ø> (-0.8572%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (-2.2327%)	⬇️
parser	∅ <ø> (∅)
br	52.6912% <ø> (+5.0301%)	⬆️

[tiancaiamao]

/test unit-test

[tiprow]

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

In response to this:

/test unit-test

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.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-06 09:27:05.015731134 +0000 UTC m=+344154.882830222: ☑️ agreed by lance6716.
• 2024-08-14 02:38:18.000159577 +0000 UTC m=+321982.703629242: ☑️ agreed by tangenta.

[yudongusa]

LGTM for the master testing, and should be turn off before released. Later to consider turn on by default when GA.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, tangenta, yudongusa

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 [lance6716,tangenta]
• pkg/sessionctx/variable/OWNERS [yudongusa]

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