-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Row not found for Global Index during DeleteOnly state of Reorganize Partition #56819
Labels
affects-8.4
component/tablepartition
This issue is related to Table Partition of TiDB.
severity/critical
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Comments
Would be fixed by #56382. |
13 tasks
jebter
added
sig/sql-infra
SIG: SQL Infra
severity/critical
component/tablepartition
This issue is related to Table Partition of TiDB.
labels
Oct 25, 2024
ti-chi-bot
bot
added
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
may-affects-8.1
labels
Oct 25, 2024
13 tasks
mjonss
removed
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
may-affects-8.1
labels
Oct 25, 2024
Since Global Index has not been GA in the previous versions, I have removed the 'may-affects-X.Y' labels for those. |
Issue is that DroppingDefinitions are excluded from the Global Index search, which is fixed in #56382. |
ti-chi-bot
pushed a commit
to ti-chi-bot/tidb
that referenced
this issue
Oct 25, 2024
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-8.4
component/tablepartition
This issue is related to Table Partition of TiDB.
severity/critical
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Apply this patch:
use
make failpoint-enable
and run the test.2. What did you expect to see? (Required)
test passing
3. What did you see instead (Required)
Read from the second SELECT did not return anything! I.e. the row "4 4" could not be found!
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: