session, table: fix listColumnPartition data race (#33199) #34285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #33199 to release-6.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/34285
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #33030
Problem Summary:
ForListColumnPruning
has a lot of fields, if we use the lock to fix data race, it will make the code dirty.So I change the way to fix #32416.
#32416 :
In step 1
In the bootstrap phase, new collation is true
After bootstrap ends, new collation is false.
In step 2
a. In the bootstrap phase, new collation is true. ForListColumnPruning builds the hashMap(generate the partition hash key, by calling
EncodeKey
) in TableFromMetab. After bootstrap ends, new collation is false. The generated partition hash key(by calling
EncodeKey
) could not be found in the hashMap.What is changed and how it works?
This way I will rebuild hashMap with
new collation is false
after step 2.a. Then we can find the key in step 2.b.Check List
Tests
Unit test
Tests already exist: TestLocatePartition
Integration test
Manual test (add detailed scripts or steps below)
new_collations_enabled_on_first_bootstrap
item to false and run the SQL statements as follows:new_collations_enabled_on_first_bootstrap = false
and execute the following statements:Side effects
Documentation
Release note