diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-09-06 17:07:49 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-09-06 17:19:07 -0400 |
| commit | 087612ed842c060ee1749b5967a226708870546b (patch) | |
| tree | 807d15d0e8e1dcb3c7a9d940971956adf3b676bb /doc/design | |
| parent | f69b019a04bbad2061ea3cfd069b502cdbcc8871 (diff) | |
fix consistency bug reading from export database
The export database has writes made to it and then expects to read back
the same data immediately. But, the way that Database.Handle does
writes, in order to support multiple writers, makes that not work, due
to caching issues. This resulted in export re-uploading files it had
already successfully renamed into place.
Fixed by allowing databases to be opened in MultiWriter or SingleWriter
mode. The export database only needs to support a single writer; it does
not make sense for multiple exports to run at the same time to the same
special remote.
All other databases still use MultiWriter mode. And by inspection,
nothing else in git-annex seems to be relying on being able to
immediately query for changes that were just written to the database.
This commit was supported by the NSF-funded DataLad project.
Diffstat (limited to 'doc/design')
| -rw-r--r-- | doc/design/exporting_trees_to_special_remotes.mdwn | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/design/exporting_trees_to_special_remotes.mdwn b/doc/design/exporting_trees_to_special_remotes.mdwn index a8247d2b9..2b5217d95 100644 --- a/doc/design/exporting_trees_to_special_remotes.mdwn +++ b/doc/design/exporting_trees_to_special_remotes.mdwn @@ -273,6 +273,7 @@ of a file when an export was interrupted.) So, before an export does anything, need to record the tree that's about to be exported to export.log, not as an exported tree, but as a goal. +Then on resume, the temp files for that can be cleaned up. ## renames and export conflicts |