nonggialiang opened a new issue, #4588:
URL: https://github.com/apache/paimon/issues/4588

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/paimon/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
   
![image](https://github.com/user-attachments/assets/76faf6ff-271b-41c8-b5b7-6b5f81c8704e)
   
   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
   
![image](https://github.com/user-attachments/assets/4a2ae11b-391f-40ad-a56c-a06e18dda05f)
   - 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)
   
![image](https://github.com/user-attachments/assets/c7221fb6-f81b-4859-bdd4-0519f76add7c)
   - time travel read from snapshot 3 (which is append) gets no output
   - time travel read from snapshot 4 (compact) or 5 (append) also 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!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to