We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Between 0.14.9 and 0.16.0 the strucutre of the bucket record changes, this leads to the system being limited in it's capabilities.
I've encountered the same problem in Project FiFo, the way I handle it is keeping all records versioned (aka bucket_0_1_0) and having a load() function that follows an upgrade path. An example: https://github.com/project-fifo/snarl/blob/dev/apps/snarl/src/snarl_org_state.erl#L48
The text was updated successfully, but these errors were encountered:
Thank you for posting this issue. We will provide the data migration tool. It would be great if you could wait for it.
Sorry, something went wrong.
We fixed this issue, which will be included in the next minor version.
leo-project/leo_s3_libs@0322d60 leo-project/leo_manager@dfcb1cb
We have included it in LeoFS v0.16.5. https://github.com/leo-project/leofs/tree/0.16.5
Thank you
yosukehara
No branches or pull requests
Between 0.14.9 and 0.16.0 the strucutre of the bucket record changes, this leads to the system being limited in it's capabilities.
I've encountered the same problem in Project FiFo, the way I handle it is keeping all records versioned (aka bucket_0_1_0) and having a load() function that follows an upgrade path. An example: https://github.com/project-fifo/snarl/blob/dev/apps/snarl/src/snarl_org_state.erl#L48
The text was updated successfully, but these errors were encountered: