kbuci commented on issue #17908: URL: https://github.com/apache/hudi/issues/17908#issuecomment-3923891773
> > ``` > In addition, regardless of the above async execution, we should ensure that it is safe for a concurrent writer to directly call performTableServices > ... > ``` Actually, let me move this out and put it in a separate issue. For context, I added this since we want a way to have our table service platform perform all MDT table services for a dataset that is no longer receiving ingestion writes to the data table. Since in our org, we can do a backfill for clustering writes on a dataset, and our internal build of HUDI we don't perform MDT table services during clustering. For this case it's fine if we hold the table lock the whole time (for table version 6) while calling `performTableServices` - but we wanted to make sure there weren't any other edge case in doing this, since although hypotetncally it should be safe we've not attempted this in production before. -- 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]
