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