test: align with TiDB clustered index behaviour

[lance6716]

What problem does this PR solve?

revert some of #1522

What is changed and how it works?

Check List

Tests

• No code

Related changes

• Need to cherry-pick to the release branch

[GMHDBJD]

Should we enable alter-primary-key in schemaTracker?

[lance6716]

Should we enable alter-primary-key in schemaTracker?

I want to set OFF clustered index in another PR, so in future we don't need to change again when update TiDB

[GMHDBJD]

I want to set OFF clustered index in another PR, so in future we don't need to change again when update TiDB

Maybe we should set it the same as downstream?

[lance6716]

I want to set OFF clustered index in another PR, so in future we don't need to change again when update TiDB

Maybe we should set it the same as downstream?

downstream may change global variable of clustered index and rebuild the table, at that time schema tracker has no way to know that change. I prefer keep schema tracker maximum compatibility of DDL.

[GMHDBJD]

/lgtm

[GMHDBJD]

Will a create table stmt create table tb(id int) from upstream become create table tb(id int nonclustered) in tracker and exec to TiDB if we set clustered index OFF

[lichunzhu]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• GMHDBJD
• lichunzhu

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[lance6716]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 59bb238

[ti-srebot]

cherry pick to release-2.0 in PR #1539