-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
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
feat: expose migration check #2074
feat: expose migration check #2074
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. This will be handy to have in our back pocket if needed.
Fo you also want to check if any indices are missing their fragment bitmap? Or is that redundant given the other checks?
python/src/lib.rs
Outdated
let dataset_ref = &dataset.as_ref(py).borrow().ds; | ||
let manifest = RT | ||
.block_on(Some(py), dataset_ref.latest_manifest())? | ||
.map_err(|err| PyIOError::new_err(format!("Failed to connect to data: {}", err)))?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems a little odd as an error message?
Oh this is for index migration? I should check the conditions for that too. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2074 +/- ##
=======================================
Coverage ? 80.70%
=======================================
Files ? 160
Lines ? 47127
Branches ? 47127
=======================================
Hits ? 38035
Misses ? 6931
Partials ? 2161
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Exposes a utility function to check whether a Dataset's manifest needs a migration to be considered the latest version. Most users have no business calling this, so it's kept in the private module.