KnightChess commented on issue #9101:
URL: https://github.com/apache/hudi/issues/9101#issuecomment-1617677280

   > Is there anyway the cleaning and archive does not trigger recomputation of 
the whole job?
   
   timeline:
    00000.commit
    00001.commit
   
   I think it is possible. The question is the table service or other 
processing logical is not in the scope of transaction. At the end of 
transaction, it mean hudi commit status is successful (00002.commit), but the 
engine job status is still running, and if it failed by other processing 
logical, the engine job will retry to make it success, so hudi will use the 
latest instance (00002.commit) snapshot to upsert, and commit again 
(00003.commit).


-- 
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