eg-kazakov commented on issue #10258: URL: https://github.com/apache/hudi/issues/10258#issuecomment-1846877533
> @eg-kazakov Hi, is the replacement commit generated by clustering or `insert overwrite`? we could skip it if it's generated by clustering, but we could not skip it if it's generated by `insert overwrite`. I believe it is insert overwrite. In my case I've switched partition deletion (by empty dataset overwrite) and regular saving operation, so my timeline looks like: ``` 2023-12-08 13:48:12 256486 20231208064747732.replacecommit 2023-12-08 13:47:59 123 20231208064747732.replacecommit.inflight 2023-12-08 13:47:51 2522 20231208064747732.replacecommit.requested 2023-12-08 13:56:59 2497730 20231208064811611.clean 2023-12-08 13:52:18 2531952 20231208064811611.clean.inflight 2023-12-08 13:52:18 2531952 20231208064811611.clean.requested ``` That does the trick for loading phase, since I do not have situation where replace commit is last operation prior loading. -- 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]
