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
Create a migrate command (ou use convert?), and only load the latest DB version available (right now it tries to be clever and load any older version, which might take a long time depending on what needs to be set)
The text was updated successfully, but these errors were encountered:
Could this be as simple as iterating over all the leaves from an old SBT and constructing a new SBT as we go? Or is that too memory intensive/inefficient?
For migrating from old to new versions we don't need to rebuild the tree structure, mostly it's about fixing the JSON.
For converting from one storage to another we might need to touch the data (hidden dirs to TarStorage, for example)
Right now the tree structure is not terribly important, but at some point it might (thinking about clustering similar leaves under the same internal node, for example). Another issue with the 'iterating over all the leaves' is rebuilding all the internal nodes when it's not really necessary to do it.
Create a migrate command (ou use convert?), and only load the latest DB version available (right now it tries to be clever and load any older version, which might take a long time depending on what needs to be set)
The text was updated successfully, but these errors were encountered: