-
Notifications
You must be signed in to change notification settings - Fork 1
Add configuration setting force_new
#73
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #73 +/- ##
==========================================
+ Coverage 99.85% 99.92% +0.07%
==========================================
Files 26 26
Lines 1372 1396 +24
==========================================
+ Hits 1370 1395 +25
+ Misses 2 1 -1 ☔ View full report in Codecov by Sentry. |
thomasstorm
left a comment
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.
Some minor suggestions, include or drop as you wish. Looks like a good feature!
Co-authored-by: Thomas Storm <thomas.storm@brockmann-consult.de>
Co-authored-by: Thomas Storm <thomas.storm@brockmann-consult.de>
Co-authored-by: Thomas Storm <thomas.storm@brockmann-consult.de>
Co-authored-by: Thomas Storm <thomas.storm@brockmann-consult.de>
Added configuration setting
force_new, which forces creation of a new target dataset. An existing target dataset (and its lock) will be permanently deleted before appending of slice datasets begins.Closes #72
Checklist (strike out non-applicable):
CHANGES.mdCHANGES.mddocs/*