*: move annotated attributes of AST node to resolve.Context

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #54436

Problem Summary:

What changed and how does it work?

move annotated attributes of AST node to a separate resolve.Context, to avoidparser pkg depends on semantic structs like TableInfo/DBInfo

This PR is one of the refactor PR to move model pkg out from parser to ddl：

• We plan to replace the un-typed arguments Args []interface{} of Job to a series of structs depends on job type, and want to add them at DDL side as they are specific to DDL and better be maintained together, but we cannot do it now as it introduced dependency cycle. Structs like Job/BackfillMeta can be moved, but TableInfo cannot as AST depends on it. I hope we can move them all together.
• Parser is a standalone go module for parsing SQL of MySQL dialect, generates AST and provides an interface to visit it. That's all that's needed if Parser is imported by other repos alone. And I guess that's one of the reasons that we make Parser independent of TiDB. TableInfo/Job/BackfillMeta and others are catalog and runtime structures specific to TiDB. They should stay in the TiDB realm.
  • AST structures are coupled with semantic catalog structures, such as ast.TableName depends on TableInfo.

Check List

Tests

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

do a TPCC performance test, the first line 8.4.0-split is this PR, the second is nightly build


sysbench

• 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

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[D3Hunter]

/test all

[tiprow]

Hi @D3Hunter. 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.

[tiprow]

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

In response to this:

/test all

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

Attention: Patch coverage is 93.61702% with 21 lines in your changes missing coverage. Please review.

Project coverage is 74.7480%. Comparing base (fa533f8) to head (5f6e03a).
Report is 2 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55634        +/-   ##
================================================
+ Coverage   72.7710%   74.7480%   +1.9770%     
================================================
  Files          1582       1586         +4     
  Lines        442822     442968       +146     
================================================
+ Hits         322246     331110      +8864     
+ Misses       100704      91581      -9123     
- Partials      19872      20277       +405     

Flag	Coverage Δ
integration	48.9993% <83.5866%> (?)
unit	71.8878% <86.0182%> (+0.0015%)	⬆️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	51.7630% <ø> (+6.3420%)	⬆️

[D3Hunter]

/test all

[tiprow]

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

In response to this:

/test all

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.

[D3Hunter]

/test all

[tiprow]

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

In response to this:

/test all

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.

[D3Hunter]

/test all

[tiprow]

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

In response to this:

/test all

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.

[D3Hunter]

/test all

[tiprow]

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

In response to this:

/test all

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.

[D3Hunter]

/retest

[tiprow]

@D3Hunter: 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.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-26 09:04:34.845791128 +0000 UTC m=+774669.980241249: ☑️ agreed by hawkingrei.
• 2024-08-26 12:32:26.346282664 +0000 UTC m=+787141.480732785: ☑️ agreed by lcwangchao.

[lcwangchao]

/test pull-lightning-integration-test

[tiprow]

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

In response to this:

/test pull-lightning-integration-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.

[D3Hunter]

/approve

for parser pkg

[ti-chi-bot]

@D3Hunter: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-lightning-integration-test	cfca5c2	link	true	/test pull-lightning-integration-test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, hawkingrei, lance6716, lcwangchao, zanmato1984

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 [D3Hunter,hawkingrei,lance6716,lcwangchao,zanmato1984]
• pkg/executor/importer/OWNERS [D3Hunter,lance6716]
• pkg/expression/OWNERS [zanmato1984]
• pkg/parser/OWNERS [D3Hunter]
• pkg/planner/OWNERS [hawkingrei]

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