Standard upload refers to uploading a single object via the TOS Java SDK putObject interface. The SDK consistently uses the InputStream class as the parameter for data streams to be uploaded. Depending on your business requirements, you may input data streams in various formats. For example, to upload strings or byte arrays, use ByteArrayInputStream; to upload files, use FileInputStream, etc. This document will provide usage instructions and sample code for uploading various data streams for your reference.

Category

Before uploading an object, you must have the tos:PutObject permission. For detailed steps, please refer to the Permission Configuration Guide.

When uploading objects, object names must comply with specific requirements. For detailed information, please refer to Object Naming Guidelines.

TOS is a distributed object storage product designed for large-scale storage, with internal partitions that store object index data. To horizontally scale the maximum throughput for uploading and downloading objects and to reduce the probability of hotspot partitions, please avoid using lexicographically incremental object naming schemes. For more information, see Performance Optimization.

If an object with the same name already exists in the bucket, the new object will overwrite the existing one. If versioning is enabled for your bucket, the original object will be retained, and a new version number will be generated to identify the newly uploaded object.

Upload String / Byte Array

The following code demonstrates how to upload a string to the file example_object.txt located in the example_dir directory of the target bucket bucket-example.

Upload Local File

There are two methods for uploading local files using the Java SDK. The first method is to pass an open FileInputStream object as a parameter to the putObject interface. The second method is to pass the path of the file to be uploaded or a File object as a parameter to the putObjectFromFile interface.

The following code demonstrates how to use the putObject interface to upload a local file, example_dir/example_file.txt, to the target bucket bucket-example, where it will be stored as example_object.txt in the example_dir directory.

The following code demonstrates how to use the putObjectFromFile interface to upload a local file example_file.txt to the example_object.txt file in the example_dir directory of the target bucket bucket-example.

Upload Network Stream

The putObject interface of the Java SDK supports uploading resources from the network to TOS. The following code demonstrates how to upload a network stream to the file example_object.txt located in the example_dir directory of the target bucket bucket-example.

Setting Object Metadata During Upload

When uploading object data using the putObject or putObjectFromFile interfaces, the SDK also supports configuring object metadata, such as specifying the object's access control ACL, storage class StorageClass, custom object metadata, etc.

The following code demonstrates how to set object metadata when using putObject. Note that this setting is optional; please make a selection according to your actual business requirements.

Processing Progress Bar During Upload

The following code demonstrates how to utilize the progress bar feature, using local file upload as an example.

Traverse Local Folder to Upload Files

The TOS Java SDK does not currently support batch uploading of files from a specified folder. You may manually traverse the local folder to upload files individually.

The following code demonstrates how to iterate through and upload a batch of files from a specified folder. To improve upload efficiency, the code sets a threshold of 100 MiB. Files smaller than 100 MiB are uploaded directly via the putObjectFromFile interface, while files equal to or larger than 100 MiB are uploaded using the uploadFile interface with resumable upload. 100MiB is provided as a reference value only; you may adjust it according to the client’s network bandwidth and other resource conditions.

Torch Object Storage