Is it possible to just optimize files between commit 0 and some commit version N? During my testing, when loading table version N and then running optimize, it looks like it just overwrites commit N+1 instead of trying to commit N+1 and then advancing to the next available version. Sounds like a bug? Or is this not possible to do?
So if N+1 already exists (say adds a some files), the overwrite then leaves those files dangling and not attached to the table, with no record of where they should go
should be able to run concurrently without corruption one another
r
Robert
04/21/2023, 6:10 AM
this should be possible. although I am not sure that we have commit conflict resolution already included in all code path. DO you have an example where taht happens?
c
Cole MacKenzie
04/21/2023, 3:21 PM
Thanks Robert - I was looking into it more and I think it might be because I am using