> ## Documentation Index > Fetch the complete documentation index at: https://docs.kinetica.com/llms.txt > Use this file to discover all available pages before exploring further. # UploadFilesRequest > UploadFilesRequest — Kinetica Java API
Package com.gpudb.protocol

Class UploadFilesRequest

java.lang.Object
com.gpudb.protocol.UploadFilesRequest
All Implemented Interfaces:
org.apache.avro.generic.GenericContainer, org.apache.avro.generic.IndexedRecord
public class UploadFilesRequest extends Object implements org.apache.avro.generic.IndexedRecord
A set of parameters for GPUdb.uploadFiles.

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 fileNames with the file names to upload into on KiFS, and their respective byte content in fileData.

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 fileNames, 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 fileData, 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 GPUdb.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 GPUdb.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: '.' '-' ':' '\[' ']' '(' ')' '#' '='.