diff options
| author | Joey Hess <joeyh@joeyh.name> | 2018-08-31 13:12:58 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2018-08-31 13:27:29 -0400 |
| commit | b3d42283ad23cbdbb281433fe42eb6110a0e28a3 (patch) | |
| tree | 45ca736248ff5b28c21bbf4b1abbd7e9fc2c3f08 /doc | |
| parent | 5c99f6247e758d2f57ac81deee2e45917d6ca352 (diff) | |
use per-remote metadata storage for S3 version ID
Since the same key can be stored in a versioned S3 bucket multiple times
with different version IDs, this allows tracking them all. Not currently
needed, but if we ever want to drop from a versioned S3 bucket, we'll
need to know them all.
This commit was supported by the NSF-funded DataLad project.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/todo/versioning_in_export_remotes.mdwn | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/doc/todo/versioning_in_export_remotes.mdwn b/doc/todo/versioning_in_export_remotes.mdwn index 34adaf1efe..e48bf1768c 100644 --- a/doc/todo/versioning_in_export_remotes.mdwn +++ b/doc/todo/versioning_in_export_remotes.mdwn @@ -82,7 +82,3 @@ keys that are not used in the current export doesn't help because another repository may have changed the exported tree and be relying on the dropped key being present in the export. Unless... Could export conflict resultion somehow detect that? - -Another reason DELETE from appendonly is not supported is that only one -version ID is stored per key, but the same key could have its content in -the bucket multiple times under different version IDs. |