You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Badger has released a new version that's format incompatible with the previous version. We have several options:
Ignore it. Not a good solution as version 1 isn't maintained.
Switch to it directly.
We'd need a migration. Badger 1 is experimental but enough users are using it that we can't just say "yolo, re-create your repos".
We'd go from a almost stable datastore right back to "we're not sure how stable this is".
Add an option to the go-ds-badger datastore to specify the underlying badger version.
Pro: this is pretty simple to implement. We should be able to import both versions of badger into go-ipfs.
Con: no way for users to opt out of the old badger if they want to decrease their binary size.
Treat it like a new datastore:
a. **Create a new go-ds-badger2 repo.&&
b. Release a v1 of go-ds-badger for badger 1, then release a v2 for badger 2. This is the "go mod" way to do this however, the go-datastore interfaces may not be stable enough to do this.
Badger has released a new version that's format incompatible with the previous version. We have several options:
a. **Create a new go-ds-badger2 repo.&&
b. Release a v1 of go-ds-badger for badger 1, then release a v2 for badger 2. This is the "go mod" way to do this however, the go-datastore interfaces may not be stable enough to do this.
I'm currently leaning towards option 3.We have gone with 4.a (thanks @Kubuxu!).
The text was updated successfully, but these errors were encountered: