The WAP feature still requires you to commit each write as a new snapshot, just don't make it as the current one. In that case, each distributed process still needs to commit their change and generate the new version file. It won't help if you want to avoid high concurrent committing.
Best, Yufei On Fri, Dec 3, 2021 at 2:06 PM Kyle Bendickson <k...@tabular.io> wrote: > This could also be achieved using the Write-Audit-Publish feature I > believe, where you audit a set of writes and then choose to publish them. > Though I'm not as familiar with that feature, but you might look into that > as well. > > Thanks, > Kyle Bendickson >
