◆ uploadFiles() [1/2]
| inline |
Uploads one or more files to KiFS.
There are two methods for uploading files: load files in their entirety, or load files in parts. The latter is recommended for files of approximately 60 MB or larger.
To upload files in their entirety, populate file_names with the file names to upload into on KiFS, and their respective byte content in file_data .
Multiple steps are involved when uploading in multiple parts. Only one file at a time can be uploaded in this manner. A user-provided UUID is utilized to tie all the upload steps together for a given file. To upload a file in multiple parts:
1. Provide the file name in file_names , the UUID in the MULTIPART_UPLOAD_UUID key in options , and a MULTIPART_OPERATION value of INIT.
2. Upload one or more parts by providing the file name, the part data in file_data , the UUID, a MULTIPART_OPERATION value of UPLOAD_PART, and the part number in the MULTIPART_UPLOAD_PART_NUMBER. The part numbers must start at 1 and increase incrementally. Parts may not be uploaded out of order.
3. Complete the upload by providing the file name, the UUID, and a MULTIPART_OPERATION value of COMPLETE.
Multipart uploads in progress may be canceled by providing the file name, the UUID, and a MULTIPART_OPERATION value of CANCEL. If an new upload is initialized with a different UUID for an existing upload in progress, the pre-existing upload is automatically canceled in favor of the new upload.
The multipart upload must be completed for the file to be usable in KiFS. Information about multipart uploads in progress is available in showFiles.
File data may be pre-encoded using base64 encoding. This should be indicated using the FILE_ENCODING option, and is recommended when using JSON serialization.
Each file path must reside in a top-level KiFS directory, i.e. one of the directories listed in showDirectories. The user must have write permission on the directory. Nested directories are permitted in file name paths. Directories are delineated with the directory separator of ’/’. For example, given the file path ‘/a/b/c/d.txt’, ‘a’ must be a KiFS directory.
These characters are allowed in file name paths: letters, numbers, spaces, the path delimiter of ’/’, and the characters: ’.’ ’-’ ’:’ ’[’ ’]’ ’(’ ’)’ ’#’ ’=’.
| file_names | An array of full file name paths to be used for the files uploaded to KiFS. File names may have any number of nested directories in their paths, but the top-level directory must be an existing KiFS directory. Each file must reside in or under a top-level directory. A full file name path cannot be larger than 1024 characters. |
| file_data | File data for the files being uploaded, for the respective files in file_names . |
| options | Optional parameters.
|
Definition at line 65708 of file KineticaFunctions.cs.
◆ uploadFiles() [2/2]
| inline |
Uploads one or more files to KiFS.
There are two methods for uploading files: load files in their entirety, or load files in parts. The latter is recommended for files of approximately 60 MB or larger.
To upload files in their entirety, populate file_names with the file names to upload into on KiFS, and their respective byte content in file_data.
Multiple steps are involved when uploading in multiple parts. Only one file at a time can be uploaded in this manner. A user-provided UUID is utilized to tie all the upload steps together for a given file. To upload a file in multiple parts:
1. Provide the file name in file_names, the UUID in the MULTIPART_UPLOAD_UUID key in options, and a MULTIPART_OPERATION value of INIT.
2. Upload one or more parts by providing the file name, the part data in file_data, the UUID, a MULTIPART_OPERATION value of UPLOAD_PART, and the part number in the MULTIPART_UPLOAD_PART_NUMBER. The part numbers must start at 1 and increase incrementally. Parts may not be uploaded out of order.
3. Complete the upload by providing the file name, the UUID, and a MULTIPART_OPERATION value of COMPLETE.
Multipart uploads in progress may be canceled by providing the file name, the UUID, and a MULTIPART_OPERATION value of CANCEL. If an new upload is initialized with a different UUID for an existing upload in progress, the pre-existing upload is automatically canceled in favor of the new upload.
The multipart upload must be completed for the file to be usable in KiFS. Information about multipart uploads in progress is available in showFiles.
File data may be pre-encoded using base64 encoding. This should be indicated using the FILE_ENCODING option, and is recommended when using JSON serialization.
Each file path must reside in a top-level KiFS directory, i.e. one of the directories listed in showDirectories. The user must have write permission on the directory. Nested directories are permitted in file name paths. Directories are delineated with the directory separator of ’/’. For example, given the file path ‘/a/b/c/d.txt’, ‘a’ must be a KiFS directory.
These characters are allowed in file name paths: letters, numbers, spaces, the path delimiter of ’/’, and the characters: ’.’ ’-’ ’:’ ’[’ ’]’ ’(’ ’)’ ’#’ ’=’.
| request_ | Request object containing the parameters for the operation. |
Definition at line 65435 of file KineticaFunctions.cs.
◆ UploadFilesAsync() [1/2]
| inline |
Uploads one or more files to KiFS.
(async)
There are two methods for uploading files: load files in their entirety, or load files in parts. The latter is recommended for files of approximately 60 MB or larger.
To upload files in their entirety, populate file_names with the file names to upload into on KiFS, and their respective byte content in file_data .
Multiple steps are involved when uploading in multiple parts. Only one file at a time can be uploaded in this manner. A user-provided UUID is utilized to tie all the upload steps together for a given file. To upload a file in multiple parts:
1. Provide the file name in file_names , the UUID in the MULTIPART_UPLOAD_UUID key in options , and a MULTIPART_OPERATION value of INIT.
2. Upload one or more parts by providing the file name, the part data in file_data , the UUID, a MULTIPART_OPERATION value of UPLOAD_PART, and the part number in the MULTIPART_UPLOAD_PART_NUMBER. The part numbers must start at 1 and increase incrementally. Parts may not be uploaded out of order.
3. Complete the upload by providing the file name, the UUID, and a MULTIPART_OPERATION value of COMPLETE.
Multipart uploads in progress may be canceled by providing the file name, the UUID, and a MULTIPART_OPERATION value of CANCEL. If an new upload is initialized with a different UUID for an existing upload in progress, the pre-existing upload is automatically canceled in favor of the new upload.
The multipart upload must be completed for the file to be usable in KiFS. Information about multipart uploads in progress is available in showFiles.
File data may be pre-encoded using base64 encoding. This should be indicated using the FILE_ENCODING option, and is recommended when using JSON serialization.
Each file path must reside in a top-level KiFS directory, i.e. one of the directories listed in showDirectories. The user must have write permission on the directory. Nested directories are permitted in file name paths. Directories are delineated with the directory separator of ’/’. For example, given the file path ‘/a/b/c/d.txt’, ‘a’ must be a KiFS directory.
These characters are allowed in file name paths: letters, numbers, spaces, the path delimiter of ’/’, and the characters: ’.’ ’-’ ’:’ ’[’ ’]’ ’(’ ’)’ ’#’ ’=’.
| file_names | An array of full file name paths to be used for the files uploaded to KiFS. File names may have any number of nested directories in their paths, but the top-level directory must be an existing KiFS directory. Each file must reside in or under a top-level directory. A full file name path cannot be larger than 1024 characters. |
| file_data | File data for the files being uploaded, for the respective files in file_names . |
| options | Optional parameters.
|
| cancellationToken | Cancellation token to cancel the operation. |
Definition at line 65909 of file KineticaFunctions.cs.
◆ UploadFilesAsync() [2/2]
| inline |
Uploads one or more files to KiFS.
(async)
There are two methods for uploading files: load files in their entirety, or load files in parts. The latter is recommended for files of approximately 60 MB or larger.
To upload files in their entirety, populate file_names with the file names to upload into on KiFS, and their respective byte content in file_data.
Multiple steps are involved when uploading in multiple parts. Only one file at a time can be uploaded in this manner. A user-provided UUID is utilized to tie all the upload steps together for a given file. To upload a file in multiple parts:
1. Provide the file name in file_names, the UUID in the MULTIPART_UPLOAD_UUID key in options, and a MULTIPART_OPERATION value of INIT.
2. Upload one or more parts by providing the file name, the part data in file_data, the UUID, a MULTIPART_OPERATION value of UPLOAD_PART, and the part number in the MULTIPART_UPLOAD_PART_NUMBER. The part numbers must start at 1 and increase incrementally. Parts may not be uploaded out of order.
3. Complete the upload by providing the file name, the UUID, and a MULTIPART_OPERATION value of COMPLETE.
Multipart uploads in progress may be canceled by providing the file name, the UUID, and a MULTIPART_OPERATION value of CANCEL. If an new upload is initialized with a different UUID for an existing upload in progress, the pre-existing upload is automatically canceled in favor of the new upload.
The multipart upload must be completed for the file to be usable in KiFS. Information about multipart uploads in progress is available in showFiles.
File data may be pre-encoded using base64 encoding. This should be indicated using the FILE_ENCODING option, and is recommended when using JSON serialization.
Each file path must reside in a top-level KiFS directory, i.e. one of the directories listed in showDirectories. The user must have write permission on the directory. Nested directories are permitted in file name paths. Directories are delineated with the directory separator of ’/’. For example, given the file path ‘/a/b/c/d.txt’, ‘a’ must be a KiFS directory.
These characters are allowed in file name paths: letters, numbers, spaces, the path delimiter of ’/’, and the characters: ’.’ ’-’ ’:’ ’[’ ’]’ ’(’ ’)’ ’#’ ’=’.
| request_ | Request object containing the parameters for the operation. |
| cancellationToken | Cancellation token to cancel the operation. |
Definition at line 65508 of file KineticaFunctions.cs.