Undesired error report when schema is changed (not null column is dropped) in rc or for-update-read. #34978
Labels
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.0
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.2
affects-6.3
affects-6.4
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-6.6
may-affects-4.0
This bug maybe affects 4.0.x versions.
severity/major
sig/transaction
SIG:Transaction
type/bug
The issue is confirmed as a bug.
Bug Report
This is another variant of #21498.
1. Minimal reproduce step (Required)
session 1
session 2
session 1
In
READ-COMMITTED
, the error is the same.2. What did you expect to see? (Required)
3. What did you see instead (Required)
ERROR 1105 (HY000): [components/tidb_query_executors/src/table_scan_executor.rs:411]: Data is corrupted, missing data for NOT NULL column (offset = 1)
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: