[Bug]: For Arctic keyd table, the out-of-order TransactionId lead to inconsistent data #479
Closed
1 task done
Labels
Milestone
What happened?
Arctic keyed table's TransactionId may be out-of order, if spark and flink write into change table at the same time.
Affects Versions
master/0.3.1
What engines are you seeing the problem on?
Core, AMS
How to reproduce
1.Spark write into change, begin transaction1, get tid = 1
2.Flink write into change, begin transaction2, get tid = 2
3.Fllink commit transaction2 with tid = 2
4.Minor Optimize transfer change files to base store with tid = 2
5.Spark commit transaction1 with tid = 1
6.Optimize/MOR will ignore change files with tid = 1, and lead to data loss
Relevant log output
No response
Anything else
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: