[GitHub] [hudi] codope commented on issue #8362: [SUPPORT] Table services with optimistic concurrency control and multiple writers

["codope (via GitHub)" <gi...@apache.org>]

codope commented on issue #8362:
URL: https://github.com/apache/hudi/issues/8362#issuecomment-1505028548

   > a lock is acquired throughout scheduling table service operations - is that how it is implemented?
   
   Yes, that is correct. Cleaner can be enabled with multi writers as well but cleaner policy has to be LAZY in that case so that cleaner is able to reconcile any conflicts before actual cleaning up the older files. With single writer, cleaning can be EAGER given that there will be no other writer to conflict with. The cleaner will depend on timeline and not on the writer. So, what really matters is the number of commits or file versions that you want to retain irrespective of whether that threshold is hit by writer 1 or writer 2.


-- 
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: commits-unsubscribe@hudi.apache.org

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