ddl: Only warn of subpartitions, still allow first level partitioning (#41207) | tidb-test=pr/2166

[ti-chi-bot]

This is an automated cherry-pick of #41207

What problem does this PR solve?

Issue Number: close #41198 , close #41200

Problem Summary:
For LIST partitioning, it did not check if SUBPARTITION was used and just stripped the subpartition part
For RANGE and HASH partitioning it stripped all partitioning and added a warning that such partitioning was not supported.

What is changed and how it works?

Combine the two behaviours:
Strip the subpartitioning from the CREATE TABLE statement and issue a warning.

Check List

Tests

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

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.

If CREATE TABLE includes subpartitions, keep the normal partitioning and skip the subpartitioning + add a warning.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

This PR also picked #38451.

[YangKeao]

/retest

[YangKeao]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-06-30 07:11:49.37402239 +0000 UTC m=+69592.748600238: ☑️ agreed by YangKeao.
• 2023-06-30 07:15:43.840864293 +0000 UTC m=+69827.215442143: ☑️ agreed by hawkingrei.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, mjonss, YangKeao

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 [YangKeao,hawkingrei,mjonss]

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

[mjonss]

This PR also picked #38451.

@YangKeao should we also update the documentation to reflect this? I.e. change 6.4.0, to 6.1.7/6.4.0, see pingcap/docs#11085

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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.