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
DM-32061: Fix some issues with export-calibs command #703
Conversation
Codecov Report
@@ Coverage Diff @@
## main #703 +/- ##
==========================================
- Coverage 84.54% 84.54% -0.01%
==========================================
Files 243 243
Lines 31785 31814 +29
Branches 5954 5963 +9
==========================================
+ Hits 26874 26896 +22
- Misses 3740 3747 +7
Partials 1171 1171
Continue to review full report at Codecov.
|
This is needed in standalone datastore tests because the metric2 template includes visit.name and standalone datastores do not have expanded dataset refs.
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.
It took a bit for me to understand the butler features I don't regularly run into, but the export code looks reasonable. I think there's one missing docstring entry (noted in its own comment).
In some scenarios a file template will be used to create the export file name and that will need metadata attached to records in our default templates.
This lets you restrict the dataset types to be exported.
move should never be allowed for export since the files must still stay with the original datastore. direct is also dangerous since we do not want files that could be moved out of the datastore on import and we do not want a direct import to have files disappear if the original butler no longer wants the file.
--transfer
and--datasets
tobutler export-calibs
export-calibs
Checklist
doc/changes