Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
movecopy [2019_12_10 12:20] – [File Copy / File Move] jim | movecopy [2020_12_30 10:11] – [Locking] jim | ||
---|---|---|---|
Line 3: | Line 3: | ||
## Copying files | ## Copying files | ||
- | Copying files from one folder or bucket to another or from one cloud provider to another can be done in the File Fabric Web File Manager | + | Copying files from one folder or bucket to another or from one storage |
The procedure for copying will be different dependent on the client used. | The procedure for copying will be different dependent on the client used. | ||
Line 9: | Line 9: | ||
How a file is copied is dependent on whether it is a single file or multiple files. | How a file is copied is dependent on whether it is a single file or multiple files. | ||
- | If a single files is copied then this may occur in a request/ | + | Prior to a Copy or Move being started |
- | If multiple files are copied then this may be delegate | + | Transfer of single files is generally synchronous. The client waits until the copy is completed. |
+ | |||
+ | If multiple files are copied then this may be delegated | ||
- | The exact method used will be dependent on the client application. | ||
### Caveats | ### Caveats | ||
Line 24: | Line 25: | ||
- Copy file to new location | - Copy file to new location | ||
- | - Move existing file to trash (where possible) | + | - Move existing file to trash (where possible |
As with copying files the procedure for moving files will be different dependent on the client application used. | As with copying files the procedure for moving files will be different dependent on the client application used. | ||
Moving files are generally executed asynchronously | Moving files are generally executed asynchronously | ||
+ | |||
+ | ##Rename | ||
+ | |||
+ | How a rename is processed is dependent on the storage. For some storage providers a rename is as simple as an API request, for others it involves: | ||
+ | |||
+ | - Copying the file as the renamed filename | ||
+ | - Removing the original file | ||
+ | |||
+ | Note that for Object Storage a rename is potentially a very expensive operation, particularly if the rename is at the folder level. This is because in Object Storage folders are actually objects and filenames actually encompass the prefix of the folder in their name so naming a folder with many files or sub folder nesting within it require every single file and folder in the hierarchy to be renamed, which itself involves a copy, a delete, and a move to Trash operation. | ||
+ | |||
###Caveats | ###Caveats | ||
Line 38: | Line 49: | ||
### Locking | ### Locking | ||
- | When files are being copied or moved locks are put in place on the parent folder to prevent other actions creating data integrity issues. These locks are removed once the operations are complete, but if this is occurring on a team folder and other users attempt to process file operations that encompass delete, update or modify then they will be unable to do so until the processes are complete. | + | When files are being copied or moved locks are put in place on the parent folder to prevent other actions creating data integrity issues. These locks are removed once the operations are complete, but if this is occurring on a team folder and other users attempt to process file operations that encompass delete, update or modify then they will be **unable to do so until the processes are complete**. |
###Audit Logs | ###Audit Logs |