Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

table partition: may be an error setting the AutoID #36661

Closed
ymkzpx opened this issue Jul 28, 2022 · 0 comments · Fixed by #36913
Closed

table partition: may be an error setting the AutoID #36661

ymkzpx opened this issue Jul 28, 2022 · 0 comments · Fixed by #36913

Comments

@ymkzpx
Copy link
Contributor

ymkzpx commented Jul 28, 2022

Enhancement

During the current Exchange partition with table DDL execution, after PutAutoID, execute updateSchemaVersion.

The following is an example of possible problems, assuming:

  • Partition table: table ID (1) AutoID KV (1) -- > 1000.
  • Non-partitioned table: table ID (2) AutoID KV (2) --- > 1000.

Execute OnExchangePartition DDL :

  • Max(AutoID KV(1),AutoID KV(2)) = 1000

After put 1000 to the partitioned table and the non-partitioned table, an insert is written to the partitioned table using Schema version old, and AutoID KV (1) is updated to 31000.

In theory, after the partition of the non-partitioned table and the partitioned table completes Exchange, in newSchemaVersion, the AutoID of the non-partitioned table should be updated to 31000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment