This repository has been archived by the owner on Jan 17, 2022. It is now read-only.
destination buckets name #28
Labels
Comments
Joacchim
added a commit
that referenced
this issue
Feb 25, 2015
- Status is now divided into:
> Store (backend + bucket/dir)
> Digest (one file for the overall obj/bytes migration status)
> Bucket (one file + one directory: listing of the files, src and dst path)
> Status of ongoing transfers (for chunked transfers) within Bucket dir.
- Status components are made Thread-safe, since they must be accessed through
their respective APIs.
- Includes the use of the proper Droplet Status Context
- Includes part of the rework for the transfer code
Addresses issue #28 (bugfix not confirmed)
WIP for issue #24
Joacchim
added a commit
that referenced
this issue
Apr 10, 2015
- Status is now divided into:
> Store (backend + bucket/dir)
> Digest (one file for the overall obj/bytes migration status)
> Bucket (one file + one directory: listing of the files, src and dst path)
> Status of ongoing transfers (for chunked transfers) within Bucket dir.
- Status components are made Thread-safe, since they must be accessed through
their respective APIs.
- Includes the use of the proper Droplet Status Context
- Includes part of the rework for the transfer code
Addresses issue #28 (bugfix not confirmed)
WIP for issue #24
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, whenever a destination bucket name is given, the tool does not try to access the bucket when creating it.
This results in an error while creating the destination bucket where sometimes, it could merely use an existing bucket.
The text was updated successfully, but these errors were encountered: