Duke-GCB / Duke-GCB/DukeDSClient
File Upload Consistency
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Due to the DukeDS eventual consistency changes files that are uploaded will have three states after a ddsclient upload command finishes.
- Uploading - file chunks have been uploaded, waiting for them to be stitched together in swift and indexed in DukeDS
- Complete - file is fully uploaded
- Error - An error occurred in combining the chunks/indexing and the file invalid
DukeDS will be adding an API endpoint to check the status of a project.
## DukeDSClient changes
- Allow a user to wait for a project to be come consistent as part of uploading. This would make it safe to script deleting the files being uploaded (current pre-eventual consistency behavior).
- Allow a user to check the status of a project
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.