innocent123 opened a new issue, #8994:
URL: https://github.com/apache/iceberg/issues/8994

   ### Query engine
   
   When I write tables with flink, I periodically manipulate metadata with 
spark, rewriteDataFiles, rewriteManifests, expireSnapshots, deleteOrphanFiles 
are created in sequence, and expireOlderThan(System.curre) is set in 
expireSnapshots ntTimeMillis()) and deleteOrphanFiles set 
olderThan(System.currentTimeMillis()). If spark succeeds in the metadata 
operation for the first time, the metadata operation for the second time is 
displayed as "File does not exist". The data file associated with manifest_file 
is missing.
   
   My question is:
   
   1. Why do I keep 1 snapshot when the data file is missing?
   
   2, Now my table query and merge operation both error, how to restore?
   
   ### Question
   
   When I write tables with flink, I periodically manipulate metadata with 
spark, rewriteDataFiles, rewriteManifests, expireSnapshots, deleteOrphanFiles 
are created in sequence, and expireOlderThan(System.curre) is set in 
expireSnapshots ntTimeMillis()) and deleteOrphanFiles set 
olderThan(System.currentTimeMillis()). If spark succeeds in the metadata 
operation for the first time, the metadata operation for the second time is 
displayed as "File does not exist". The data file associated with manifest_file 
is missing.
   
   My question is:
   
   1. Why do I keep 1 snapshot when the data file is missing?
   
   2, Now my table query and merge operation both error, how to restore?


-- 
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: issues-unsubscr...@iceberg.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to