@Generated(value="software.amazon.awssdk:codegen") @ThreadSafe public interface BackupStorageAsyncClient extends AwsClient
builder() method.
The frontend service for Cryo Storage.| Modifier and Type | Field and Description |
|---|---|
static String |
SERVICE_METADATA_ID
Value for looking up the service's metadata from the
ServiceMetadataProvider. |
static String |
SERVICE_NAME |
| Modifier and Type | Method and Description |
|---|---|
static BackupStorageAsyncClientBuilder |
builder()
Create a builder that can be used to configure and create a
BackupStorageAsyncClient. |
static BackupStorageAsyncClient |
create()
Create a
BackupStorageAsyncClient with the region loaded from the
DefaultAwsRegionProviderChain and credentials loaded from the
DefaultCredentialsProvider. |
default CompletableFuture<DeleteObjectResponse> |
deleteObject(Consumer<DeleteObjectRequest.Builder> deleteObjectRequest)
Delete Object from the incremental base Backup.
|
default CompletableFuture<DeleteObjectResponse> |
deleteObject(DeleteObjectRequest deleteObjectRequest)
Delete Object from the incremental base Backup.
|
default <ReturnT> CompletableFuture<ReturnT> |
getChunk(Consumer<GetChunkRequest.Builder> getChunkRequest,
AsyncResponseTransformer<GetChunkResponse,ReturnT> asyncResponseTransformer)
Gets the specified object's chunk.
|
default CompletableFuture<GetChunkResponse> |
getChunk(Consumer<GetChunkRequest.Builder> getChunkRequest,
Path destinationPath)
Gets the specified object's chunk.
|
default <ReturnT> CompletableFuture<ReturnT> |
getChunk(GetChunkRequest getChunkRequest,
AsyncResponseTransformer<GetChunkResponse,ReturnT> asyncResponseTransformer)
Gets the specified object's chunk.
|
default CompletableFuture<GetChunkResponse> |
getChunk(GetChunkRequest getChunkRequest,
Path destinationPath)
Gets the specified object's chunk.
|
default <ReturnT> CompletableFuture<ReturnT> |
getObjectMetadata(Consumer<GetObjectMetadataRequest.Builder> getObjectMetadataRequest,
AsyncResponseTransformer<GetObjectMetadataResponse,ReturnT> asyncResponseTransformer)
Get metadata associated with an Object.
|
default CompletableFuture<GetObjectMetadataResponse> |
getObjectMetadata(Consumer<GetObjectMetadataRequest.Builder> getObjectMetadataRequest,
Path destinationPath)
Get metadata associated with an Object.
|
default <ReturnT> CompletableFuture<ReturnT> |
getObjectMetadata(GetObjectMetadataRequest getObjectMetadataRequest,
AsyncResponseTransformer<GetObjectMetadataResponse,ReturnT> asyncResponseTransformer)
Get metadata associated with an Object.
|
default CompletableFuture<GetObjectMetadataResponse> |
getObjectMetadata(GetObjectMetadataRequest getObjectMetadataRequest,
Path destinationPath)
Get metadata associated with an Object.
|
default CompletableFuture<ListChunksResponse> |
listChunks(Consumer<ListChunksRequest.Builder> listChunksRequest)
List chunks in a given Object
|
default CompletableFuture<ListChunksResponse> |
listChunks(ListChunksRequest listChunksRequest)
List chunks in a given Object
|
default ListChunksPublisher |
listChunksPaginator(Consumer<ListChunksRequest.Builder> listChunksRequest)
List chunks in a given Object
|
default ListChunksPublisher |
listChunksPaginator(ListChunksRequest listChunksRequest)
List chunks in a given Object
|
default CompletableFuture<ListObjectsResponse> |
listObjects(Consumer<ListObjectsRequest.Builder> listObjectsRequest)
List all Objects in a given Backup.
|
default CompletableFuture<ListObjectsResponse> |
listObjects(ListObjectsRequest listObjectsRequest)
List all Objects in a given Backup.
|
default ListObjectsPublisher |
listObjectsPaginator(Consumer<ListObjectsRequest.Builder> listObjectsRequest)
List all Objects in a given Backup.
|
default ListObjectsPublisher |
listObjectsPaginator(ListObjectsRequest listObjectsRequest)
List all Objects in a given Backup.
|
default CompletableFuture<NotifyObjectCompleteResponse> |
notifyObjectComplete(Consumer<NotifyObjectCompleteRequest.Builder> notifyObjectCompleteRequest,
AsyncRequestBody requestBody)
Complete upload
|
default CompletableFuture<NotifyObjectCompleteResponse> |
notifyObjectComplete(Consumer<NotifyObjectCompleteRequest.Builder> notifyObjectCompleteRequest,
Path sourcePath)
Complete upload
|
default CompletableFuture<NotifyObjectCompleteResponse> |
notifyObjectComplete(NotifyObjectCompleteRequest notifyObjectCompleteRequest,
AsyncRequestBody requestBody)
Complete upload
|
default CompletableFuture<NotifyObjectCompleteResponse> |
notifyObjectComplete(NotifyObjectCompleteRequest notifyObjectCompleteRequest,
Path sourcePath)
Complete upload
|
default CompletableFuture<PutChunkResponse> |
putChunk(Consumer<PutChunkRequest.Builder> putChunkRequest,
AsyncRequestBody requestBody)
Upload chunk.
|
default CompletableFuture<PutChunkResponse> |
putChunk(Consumer<PutChunkRequest.Builder> putChunkRequest,
Path sourcePath)
Upload chunk.
|
default CompletableFuture<PutChunkResponse> |
putChunk(PutChunkRequest putChunkRequest,
AsyncRequestBody requestBody)
Upload chunk.
|
default CompletableFuture<PutChunkResponse> |
putChunk(PutChunkRequest putChunkRequest,
Path sourcePath)
Upload chunk.
|
default CompletableFuture<PutObjectResponse> |
putObject(Consumer<PutObjectRequest.Builder> putObjectRequest,
AsyncRequestBody requestBody)
Upload object that can store object metadata String and data blob in single API call using inline chunk field.
|
default CompletableFuture<PutObjectResponse> |
putObject(Consumer<PutObjectRequest.Builder> putObjectRequest,
Path sourcePath)
Upload object that can store object metadata String and data blob in single API call using inline chunk field.
|
default CompletableFuture<PutObjectResponse> |
putObject(PutObjectRequest putObjectRequest,
AsyncRequestBody requestBody)
Upload object that can store object metadata String and data blob in single API call using inline chunk field.
|
default CompletableFuture<PutObjectResponse> |
putObject(PutObjectRequest putObjectRequest,
Path sourcePath)
Upload object that can store object metadata String and data blob in single API call using inline chunk field.
|
default BackupStorageServiceClientConfiguration |
serviceClientConfiguration() |
default CompletableFuture<StartObjectResponse> |
startObject(Consumer<StartObjectRequest.Builder> startObjectRequest)
Start upload containing one or many chunks.
|
default CompletableFuture<StartObjectResponse> |
startObject(StartObjectRequest startObjectRequest)
Start upload containing one or many chunks.
|
serviceNameclosestatic final String SERVICE_NAME
static final String SERVICE_METADATA_ID
ServiceMetadataProvider.default CompletableFuture<DeleteObjectResponse> deleteObject(DeleteObjectRequest deleteObjectRequest)
deleteObjectRequest - default CompletableFuture<DeleteObjectResponse> deleteObject(Consumer<DeleteObjectRequest.Builder> deleteObjectRequest)
This is a convenience which creates an instance of the DeleteObjectRequest.Builder avoiding the need to
create one manually via DeleteObjectRequest.builder()
deleteObjectRequest - A Consumer that will call methods on
DeleteObjectRequest.Builder to create a
request.default <ReturnT> CompletableFuture<ReturnT> getChunk(GetChunkRequest getChunkRequest, AsyncResponseTransformer<GetChunkResponse,ReturnT> asyncResponseTransformer)
getChunkRequest - asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See
AsyncResponseTransformer for details on how this callback should be implemented and for links to
precanned implementations for common scenarios like downloading to a file. The service documentation for
the response content is as follows 'Chunk data'.default <ReturnT> CompletableFuture<ReturnT> getChunk(Consumer<GetChunkRequest.Builder> getChunkRequest, AsyncResponseTransformer<GetChunkResponse,ReturnT> asyncResponseTransformer)
This is a convenience which creates an instance of the GetChunkRequest.Builder avoiding the need to
create one manually via GetChunkRequest.builder()
getChunkRequest - A Consumer that will call methods on
GetChunkRequest.Builder to create a request.asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See
AsyncResponseTransformer for details on how this callback should be implemented and for links to
precanned implementations for common scenarios like downloading to a file. The service documentation for
the response content is as follows 'Chunk data'.default CompletableFuture<GetChunkResponse> getChunk(GetChunkRequest getChunkRequest, Path destinationPath)
getChunkRequest - destinationPath - Path to file that response contents will be written to. The file must not exist or this method
will throw an exception. If the file is not writable by the current user then an exception will be thrown.
The service documentation for the response content is as follows 'Chunk data'.default CompletableFuture<GetChunkResponse> getChunk(Consumer<GetChunkRequest.Builder> getChunkRequest, Path destinationPath)
This is a convenience which creates an instance of the GetChunkRequest.Builder avoiding the need to
create one manually via GetChunkRequest.builder()
getChunkRequest - A Consumer that will call methods on
GetChunkRequest.Builder to create a request.destinationPath - Path to file that response contents will be written to. The file must not exist or this method
will throw an exception. If the file is not writable by the current user then an exception will be thrown.
The service documentation for the response content is as follows 'Chunk data'.default <ReturnT> CompletableFuture<ReturnT> getObjectMetadata(GetObjectMetadataRequest getObjectMetadataRequest, AsyncResponseTransformer<GetObjectMetadataResponse,ReturnT> asyncResponseTransformer)
getObjectMetadataRequest - asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See
AsyncResponseTransformer for details on how this callback should be implemented and for links to
precanned implementations for common scenarios like downloading to a file. The service documentation for
the response content is as follows 'Metadata blob.'.default <ReturnT> CompletableFuture<ReturnT> getObjectMetadata(Consumer<GetObjectMetadataRequest.Builder> getObjectMetadataRequest, AsyncResponseTransformer<GetObjectMetadataResponse,ReturnT> asyncResponseTransformer)
This is a convenience which creates an instance of the GetObjectMetadataRequest.Builder avoiding the need
to create one manually via GetObjectMetadataRequest.builder()
getObjectMetadataRequest - A Consumer that will call methods on
GetObjectMetadataRequest.Builder to create a
request.asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See
AsyncResponseTransformer for details on how this callback should be implemented and for links to
precanned implementations for common scenarios like downloading to a file. The service documentation for
the response content is as follows 'Metadata blob.'.default CompletableFuture<GetObjectMetadataResponse> getObjectMetadata(GetObjectMetadataRequest getObjectMetadataRequest, Path destinationPath)
getObjectMetadataRequest - destinationPath - Path to file that response contents will be written to. The file must not exist or this method
will throw an exception. If the file is not writable by the current user then an exception will be thrown.
The service documentation for the response content is as follows 'Metadata blob.'.default CompletableFuture<GetObjectMetadataResponse> getObjectMetadata(Consumer<GetObjectMetadataRequest.Builder> getObjectMetadataRequest, Path destinationPath)
This is a convenience which creates an instance of the GetObjectMetadataRequest.Builder avoiding the need
to create one manually via GetObjectMetadataRequest.builder()
getObjectMetadataRequest - A Consumer that will call methods on
GetObjectMetadataRequest.Builder to create a
request.destinationPath - Path to file that response contents will be written to. The file must not exist or this method
will throw an exception. If the file is not writable by the current user then an exception will be thrown.
The service documentation for the response content is as follows 'Metadata blob.'.default CompletableFuture<ListChunksResponse> listChunks(ListChunksRequest listChunksRequest)
listChunksRequest - default CompletableFuture<ListChunksResponse> listChunks(Consumer<ListChunksRequest.Builder> listChunksRequest)
This is a convenience which creates an instance of the ListChunksRequest.Builder avoiding the need to
create one manually via ListChunksRequest.builder()
listChunksRequest - A Consumer that will call methods on
ListChunksRequest.Builder to create a request.default ListChunksPublisher listChunksPaginator(ListChunksRequest listChunksRequest)
This is a variant of listChunks(software.amazon.awssdk.services.backupstorage.model.ListChunksRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.backupstorage.paginators.ListChunksPublisher publisher = client.listChunksPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.backupstorage.paginators.ListChunksPublisher publisher = client.listChunksPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.backupstorage.model.ListChunksResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.backupstorage.model.ListChunksResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listChunks(software.amazon.awssdk.services.backupstorage.model.ListChunksRequest) operation.
listChunksRequest - default ListChunksPublisher listChunksPaginator(Consumer<ListChunksRequest.Builder> listChunksRequest)
This is a variant of listChunks(software.amazon.awssdk.services.backupstorage.model.ListChunksRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.backupstorage.paginators.ListChunksPublisher publisher = client.listChunksPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.backupstorage.paginators.ListChunksPublisher publisher = client.listChunksPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.backupstorage.model.ListChunksResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.backupstorage.model.ListChunksResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listChunks(software.amazon.awssdk.services.backupstorage.model.ListChunksRequest) operation.
This is a convenience which creates an instance of the ListChunksRequest.Builder avoiding the need to
create one manually via ListChunksRequest.builder()
listChunksRequest - A Consumer that will call methods on
ListChunksRequest.Builder to create a request.default CompletableFuture<ListObjectsResponse> listObjects(ListObjectsRequest listObjectsRequest)
listObjectsRequest - default CompletableFuture<ListObjectsResponse> listObjects(Consumer<ListObjectsRequest.Builder> listObjectsRequest)
This is a convenience which creates an instance of the ListObjectsRequest.Builder avoiding the need to
create one manually via ListObjectsRequest.builder()
listObjectsRequest - A Consumer that will call methods on
ListObjectsRequest.Builder to create a
request.default ListObjectsPublisher listObjectsPaginator(ListObjectsRequest listObjectsRequest)
This is a variant of listObjects(software.amazon.awssdk.services.backupstorage.model.ListObjectsRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.backupstorage.paginators.ListObjectsPublisher publisher = client.listObjectsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.backupstorage.paginators.ListObjectsPublisher publisher = client.listObjectsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.backupstorage.model.ListObjectsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.backupstorage.model.ListObjectsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listObjects(software.amazon.awssdk.services.backupstorage.model.ListObjectsRequest) operation.
listObjectsRequest - default ListObjectsPublisher listObjectsPaginator(Consumer<ListObjectsRequest.Builder> listObjectsRequest)
This is a variant of listObjects(software.amazon.awssdk.services.backupstorage.model.ListObjectsRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.backupstorage.paginators.ListObjectsPublisher publisher = client.listObjectsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.backupstorage.paginators.ListObjectsPublisher publisher = client.listObjectsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.backupstorage.model.ListObjectsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.backupstorage.model.ListObjectsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listObjects(software.amazon.awssdk.services.backupstorage.model.ListObjectsRequest) operation.
This is a convenience which creates an instance of the ListObjectsRequest.Builder avoiding the need to
create one manually via ListObjectsRequest.builder()
listObjectsRequest - A Consumer that will call methods on
ListObjectsRequest.Builder to create a
request.default CompletableFuture<NotifyObjectCompleteResponse> notifyObjectComplete(NotifyObjectCompleteRequest notifyObjectCompleteRequest, AsyncRequestBody requestBody)
notifyObjectCompleteRequest - requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The
size of the content is expected to be known up front. See AsyncRequestBody for specific details on
implementing this interface as well as links to precanned implementations for common scenarios like
uploading from a file. The service documentation for the request content is as follows 'Optional metadata
associated with an Object. Maximum length is 4MB.'default CompletableFuture<NotifyObjectCompleteResponse> notifyObjectComplete(Consumer<NotifyObjectCompleteRequest.Builder> notifyObjectCompleteRequest, AsyncRequestBody requestBody)
This is a convenience which creates an instance of the NotifyObjectCompleteRequest.Builder avoiding the
need to create one manually via NotifyObjectCompleteRequest.builder()
notifyObjectCompleteRequest - A Consumer that will call methods on
NotifyObjectCompleteRequest.Builder to create
a request.requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The
size of the content is expected to be known up front. See AsyncRequestBody for specific details on
implementing this interface as well as links to precanned implementations for common scenarios like
uploading from a file. The service documentation for the request content is as follows 'Optional metadata
associated with an Object. Maximum length is 4MB.'default CompletableFuture<NotifyObjectCompleteResponse> notifyObjectComplete(NotifyObjectCompleteRequest notifyObjectCompleteRequest, Path sourcePath)
notifyObjectCompleteRequest - sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read
multiple times in the event of a retry. If the file does not exist or the current user does not have
access to read it then an exception will be thrown. The service documentation for the request content is
as follows 'Optional metadata associated with an Object. Maximum length is 4MB.'default CompletableFuture<NotifyObjectCompleteResponse> notifyObjectComplete(Consumer<NotifyObjectCompleteRequest.Builder> notifyObjectCompleteRequest, Path sourcePath)
This is a convenience which creates an instance of the NotifyObjectCompleteRequest.Builder avoiding the
need to create one manually via NotifyObjectCompleteRequest.builder()
notifyObjectCompleteRequest - A Consumer that will call methods on
NotifyObjectCompleteRequest.Builder to create
a request.sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read
multiple times in the event of a retry. If the file does not exist or the current user does not have
access to read it then an exception will be thrown. The service documentation for the request content is
as follows 'Optional metadata associated with an Object. Maximum length is 4MB.'default CompletableFuture<PutChunkResponse> putChunk(PutChunkRequest putChunkRequest, AsyncRequestBody requestBody)
putChunkRequest - requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The
size of the content is expected to be known up front. See AsyncRequestBody for specific details on
implementing this interface as well as links to precanned implementations for common scenarios like
uploading from a file. The service documentation for the request content is as follows 'Data to be
uploaded'default CompletableFuture<PutChunkResponse> putChunk(Consumer<PutChunkRequest.Builder> putChunkRequest, AsyncRequestBody requestBody)
This is a convenience which creates an instance of the PutChunkRequest.Builder avoiding the need to
create one manually via PutChunkRequest.builder()
putChunkRequest - A Consumer that will call methods on
PutChunkRequest.Builder to create a request.requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The
size of the content is expected to be known up front. See AsyncRequestBody for specific details on
implementing this interface as well as links to precanned implementations for common scenarios like
uploading from a file. The service documentation for the request content is as follows 'Data to be
uploaded'default CompletableFuture<PutChunkResponse> putChunk(PutChunkRequest putChunkRequest, Path sourcePath)
putChunkRequest - sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read
multiple times in the event of a retry. If the file does not exist or the current user does not have
access to read it then an exception will be thrown. The service documentation for the request content is
as follows 'Data to be uploaded'default CompletableFuture<PutChunkResponse> putChunk(Consumer<PutChunkRequest.Builder> putChunkRequest, Path sourcePath)
This is a convenience which creates an instance of the PutChunkRequest.Builder avoiding the need to
create one manually via PutChunkRequest.builder()
putChunkRequest - A Consumer that will call methods on
PutChunkRequest.Builder to create a request.sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read
multiple times in the event of a retry. If the file does not exist or the current user does not have
access to read it then an exception will be thrown. The service documentation for the request content is
as follows 'Data to be uploaded'default CompletableFuture<PutObjectResponse> putObject(PutObjectRequest putObjectRequest, AsyncRequestBody requestBody)
putObjectRequest - requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The
size of the content is expected to be known up front. See AsyncRequestBody for specific details on
implementing this interface as well as links to precanned implementations for common scenarios like
uploading from a file. The service documentation for the request content is as follows 'Inline chunk data
to be uploaded.'default CompletableFuture<PutObjectResponse> putObject(Consumer<PutObjectRequest.Builder> putObjectRequest, AsyncRequestBody requestBody)
This is a convenience which creates an instance of the PutObjectRequest.Builder avoiding the need to
create one manually via PutObjectRequest.builder()
putObjectRequest - A Consumer that will call methods on
PutObjectRequest.Builder to create a request.requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The
size of the content is expected to be known up front. See AsyncRequestBody for specific details on
implementing this interface as well as links to precanned implementations for common scenarios like
uploading from a file. The service documentation for the request content is as follows 'Inline chunk data
to be uploaded.'default CompletableFuture<PutObjectResponse> putObject(PutObjectRequest putObjectRequest, Path sourcePath)
putObjectRequest - sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read
multiple times in the event of a retry. If the file does not exist or the current user does not have
access to read it then an exception will be thrown. The service documentation for the request content is
as follows 'Inline chunk data to be uploaded.'default CompletableFuture<PutObjectResponse> putObject(Consumer<PutObjectRequest.Builder> putObjectRequest, Path sourcePath)
This is a convenience which creates an instance of the PutObjectRequest.Builder avoiding the need to
create one manually via PutObjectRequest.builder()
putObjectRequest - A Consumer that will call methods on
PutObjectRequest.Builder to create a request.sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read
multiple times in the event of a retry. If the file does not exist or the current user does not have
access to read it then an exception will be thrown. The service documentation for the request content is
as follows 'Inline chunk data to be uploaded.'default CompletableFuture<StartObjectResponse> startObject(StartObjectRequest startObjectRequest)
startObjectRequest - default CompletableFuture<StartObjectResponse> startObject(Consumer<StartObjectRequest.Builder> startObjectRequest)
This is a convenience which creates an instance of the StartObjectRequest.Builder avoiding the need to
create one manually via StartObjectRequest.builder()
startObjectRequest - A Consumer that will call methods on
StartObjectRequest.Builder to create a
request.default BackupStorageServiceClientConfiguration serviceClientConfiguration()
serviceClientConfiguration in interface AwsClientserviceClientConfiguration in interface SdkClientstatic BackupStorageAsyncClient create()
BackupStorageAsyncClient with the region loaded from the
DefaultAwsRegionProviderChain and credentials loaded from the
DefaultCredentialsProvider.static BackupStorageAsyncClientBuilder builder()
BackupStorageAsyncClient.Copyright © 2023. All rights reserved.