You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched in the issues and found nothing similar.
Paimon version
0.8
Compute Engine
flink 1.7
Minimal reproduce step
1、streaming write into a paimon table with deletion-vector enabled
2、choose a key in the table and run a batch statement to 'delete from' the paimon table
select * from paimon.test_fts.test_dvdown_1125 where k = '039f61ff8228b6515b88f0dcf1afaec41ccc3fd7614ff4763fa82dfd23455e127036eb152bc444fa34392dd42f92dbbccc67'
3、batch read from the paimon table with the key
if we run the above select after 'delete from' and before streaming job taking a checkpoint : the output is empty
if we run the above select after the checkpoint succeeding 'delete from': the key comes out again
What doesn't meet your expectations?
The key is not deleted successfully.
We can also reproduce the weird issue with batch time travel:
With a snapshots history like below (snapshot 3 and 4 committed by 'delete from' , and others by streaming job)
time travel read from snapshot 3 (which is append) gets the key
time travel read from snapshot 4 (compact) or 5 (append) gets no output
time travel read from snapshot 6 (compact) gets the key
Anything else?
No response
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Paimon version
0.8
Compute Engine
flink 1.7
Minimal reproduce step
1、streaming write into a paimon table with deletion-vector enabled
2、choose a key in the table and run a batch statement to 'delete from' the paimon table
3、batch read from the paimon table with the key
What doesn't meet your expectations?
The key is not deleted successfully.
We can also reproduce the weird issue with batch time travel:
With a snapshots history like below (snapshot 3 and 4 committed by 'delete from' , and others by streaming job)
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: