"Indices can be corrupted if you do not plan accordingly."
ghazel opened this issue · comments
The "version" section of the documentation has an ominous "Indices can be corrupted if you do not plan accordingly." warning. How exactly should one plan accordingly? Couldn't the migration process be solved with some sort of locking, or simply with an entirely different versioned key namespace?
Probably. However, given that the author didn't finish all the TODOs I think it was a lot to ask of him to flush out the finer points of the design. Instead it's left to implementers to be wise with migrations, there are really only a few gotca's.