/*
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License").
* You may not use this file except in compliance with the License.
* A copy of the License is located at
*
* http://aws.amazon.com/apache2.0
*
* or in the "license" file accompanying this file. This file is distributed
* on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
* express or implied. See the License for the specific language governing
* permissions and limitations under the License.
*/
/*
* Do not modify this file. This file is generated from the dynamodb-2012-08-10.normal.json service model.
*/
using System;
using System.Runtime.ExceptionServices;
using System.Threading;
using System.Threading.Tasks;
using System.Collections.Generic;
using System.Net;
using Amazon.DynamoDBv2.Model;
using Amazon.DynamoDBv2.Model.Internal.MarshallTransformations;
using Amazon.DynamoDBv2.Internal;
using Amazon.Runtime;
using Amazon.Runtime.Internal;
using Amazon.Runtime.Internal.Auth;
using Amazon.Runtime.Internal.Transform;
namespace Amazon.DynamoDBv2
{
///
/// Implementation for accessing DynamoDB
///
/// Amazon DynamoDB
///
/// Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable
/// performance with seamless scalability. DynamoDB lets you offload the administrative
/// burdens of operating and scaling a distributed database, so that you don't have to
/// worry about hardware provisioning, setup and configuration, replication, software
/// patching, or cluster scaling.
///
///
///
/// With DynamoDB, you can create database tables that can store and retrieve any amount
/// of data, and serve any level of request traffic. You can scale up or scale down your
/// tables' throughput capacity without downtime or performance degradation, and use the
/// Amazon Web Services Management Console to monitor resource utilization and performance
/// metrics.
///
///
///
/// DynamoDB automatically spreads the data and traffic for your tables over a sufficient
/// number of servers to handle your throughput and storage requirements, while maintaining
/// consistent and fast performance. All of your data is stored on solid state disks (SSDs)
/// and automatically replicated across multiple Availability Zones in an Amazon Web Services
/// Region, providing built-in high availability and data durability.
///
///
public partial class AmazonDynamoDBClient : AmazonServiceClient, IAmazonDynamoDB
{
private static IServiceMetadata serviceMetadata = new AmazonDynamoDBMetadata();
#region Constructors
///
/// Constructs AmazonDynamoDBClient with the credentials loaded from the application's
/// default configuration, and if unsuccessful from the Instance Profile service on an EC2 instance.
///
/// Example App.config with credentials set.
///
/// <?xml version="1.0" encoding="utf-8" ?>
/// <configuration>
/// <appSettings>
/// <add key="AWSProfileName" value="AWS Default"/>
/// </appSettings>
/// </configuration>
///
///
///
public AmazonDynamoDBClient()
: base(FallbackCredentialsFactory.GetCredentials(), new AmazonDynamoDBConfig()) { }
///
/// Constructs AmazonDynamoDBClient with the credentials loaded from the application's
/// default configuration, and if unsuccessful from the Instance Profile service on an EC2 instance.
///
/// Example App.config with credentials set.
///
/// <?xml version="1.0" encoding="utf-8" ?>
/// <configuration>
/// <appSettings>
/// <add key="AWSProfileName" value="AWS Default"/>
/// </appSettings>
/// </configuration>
///
///
///
/// The region to connect.
public AmazonDynamoDBClient(RegionEndpoint region)
: base(FallbackCredentialsFactory.GetCredentials(), new AmazonDynamoDBConfig{RegionEndpoint = region}) { }
///
/// Constructs AmazonDynamoDBClient with the credentials loaded from the application's
/// default configuration, and if unsuccessful from the Instance Profile service on an EC2 instance.
///
/// Example App.config with credentials set.
///
/// <?xml version="1.0" encoding="utf-8" ?>
/// <configuration>
/// <appSettings>
/// <add key="AWSProfileName" value="AWS Default"/>
/// </appSettings>
/// </configuration>
///
///
///
/// The AmazonDynamoDBClient Configuration Object
public AmazonDynamoDBClient(AmazonDynamoDBConfig config)
: base(FallbackCredentialsFactory.GetCredentials(config), config){}
///
/// Constructs AmazonDynamoDBClient with AWS Credentials
///
/// AWS Credentials
public AmazonDynamoDBClient(AWSCredentials credentials)
: this(credentials, new AmazonDynamoDBConfig())
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Credentials
///
/// AWS Credentials
/// The region to connect.
public AmazonDynamoDBClient(AWSCredentials credentials, RegionEndpoint region)
: this(credentials, new AmazonDynamoDBConfig{RegionEndpoint = region})
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Credentials and an
/// AmazonDynamoDBClient Configuration object.
///
/// AWS Credentials
/// The AmazonDynamoDBClient Configuration Object
public AmazonDynamoDBClient(AWSCredentials credentials, AmazonDynamoDBConfig clientConfig)
: base(credentials, clientConfig)
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Access Key ID and AWS Secret Key
///
/// AWS Access Key ID
/// AWS Secret Access Key
public AmazonDynamoDBClient(string awsAccessKeyId, string awsSecretAccessKey)
: this(awsAccessKeyId, awsSecretAccessKey, new AmazonDynamoDBConfig())
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Access Key ID and AWS Secret Key
///
/// AWS Access Key ID
/// AWS Secret Access Key
/// The region to connect.
public AmazonDynamoDBClient(string awsAccessKeyId, string awsSecretAccessKey, RegionEndpoint region)
: this(awsAccessKeyId, awsSecretAccessKey, new AmazonDynamoDBConfig() {RegionEndpoint=region})
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Access Key ID, AWS Secret Key and an
/// AmazonDynamoDBClient Configuration object.
///
/// AWS Access Key ID
/// AWS Secret Access Key
/// The AmazonDynamoDBClient Configuration Object
public AmazonDynamoDBClient(string awsAccessKeyId, string awsSecretAccessKey, AmazonDynamoDBConfig clientConfig)
: base(awsAccessKeyId, awsSecretAccessKey, clientConfig)
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Access Key ID and AWS Secret Key
///
/// AWS Access Key ID
/// AWS Secret Access Key
/// AWS Session Token
public AmazonDynamoDBClient(string awsAccessKeyId, string awsSecretAccessKey, string awsSessionToken)
: this(awsAccessKeyId, awsSecretAccessKey, awsSessionToken, new AmazonDynamoDBConfig())
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Access Key ID and AWS Secret Key
///
/// AWS Access Key ID
/// AWS Secret Access Key
/// AWS Session Token
/// The region to connect.
public AmazonDynamoDBClient(string awsAccessKeyId, string awsSecretAccessKey, string awsSessionToken, RegionEndpoint region)
: this(awsAccessKeyId, awsSecretAccessKey, awsSessionToken, new AmazonDynamoDBConfig{RegionEndpoint = region})
{
}
///
/// Constructs AmazonDynamoDBClient with AWS Access Key ID, AWS Secret Key and an
/// AmazonDynamoDBClient Configuration object.
///
/// AWS Access Key ID
/// AWS Secret Access Key
/// AWS Session Token
/// The AmazonDynamoDBClient Configuration Object
public AmazonDynamoDBClient(string awsAccessKeyId, string awsSecretAccessKey, string awsSessionToken, AmazonDynamoDBConfig clientConfig)
: base(awsAccessKeyId, awsSecretAccessKey, awsSessionToken, clientConfig)
{
}
#endregion
#if AWS_ASYNC_ENUMERABLES_API
private IDynamoDBv2PaginatorFactory _paginators;
///
/// Paginators for the service
///
public IDynamoDBv2PaginatorFactory Paginators
{
get
{
if (this._paginators == null)
{
this._paginators = new DynamoDBv2PaginatorFactory(this);
}
return this._paginators;
}
}
#endif
#region Overrides
///
/// Creates the signer for the service.
///
protected override AbstractAWSSigner CreateSigner()
{
return new AWS4Signer();
}
///
/// Customizes the runtime pipeline.
///
/// Runtime pipeline for the current client.
protected override void CustomizeRuntimePipeline(RuntimePipeline pipeline)
{
if(this.Config.RetryMode == RequestRetryMode.Legacy)
{
pipeline.ReplaceHandler(new Amazon.Runtime.Internal.RetryHandler(new Amazon.DynamoDBv2.Internal.DynamoDBRetryPolicy(this.Config)));
}
pipeline.RemoveHandler();
pipeline.AddHandlerAfter(new AmazonDynamoDBEndpointResolver());
}
///
/// Capture metadata for the service.
///
protected override IServiceMetadata ServiceMetadata
{
get
{
return serviceMetadata;
}
}
#endregion
#region Dispose
///
/// Disposes the service client.
///
protected override void Dispose(bool disposing)
{
base.Dispose(disposing);
}
#endregion
#region EndpointOperation Override
protected override IEnumerable EndpointOperation(EndpointOperationContextBase context)
{
return EndpointDiscoveryResolver.ResolveEndpoints(context, () =>
{
var request = new DescribeEndpointsRequest
{
};
var response = DescribeEndpoints(request);
if(response.HttpStatusCode != HttpStatusCode.OK || response.Endpoints == null)
{
return null;
}
var endpoints = new List();
foreach(var endpoint in response.Endpoints)
{
endpoints.Add(new DiscoveryEndpoint(endpoint.Address, endpoint.CachePeriodInMinutes));
}
return endpoints;
});
}
#endregion
#region BatchExecuteStatement
internal virtual BatchExecuteStatementResponse BatchExecuteStatement(BatchExecuteStatementRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = BatchExecuteStatementRequestMarshaller.Instance;
options.ResponseUnmarshaller = BatchExecuteStatementResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// This operation allows you to perform batch reads or writes on data stored in DynamoDB,
/// using PartiQL. Each read statement in a BatchExecuteStatement must specify
/// an equality condition on all key attributes. This enforces that each SELECT
/// statement in a batch returns at most a single item.
///
///
///
/// The entire batch must consist of either read statements or write statements, you cannot
/// mix both in one batch.
///
///
///
/// A HTTP 200 response does not mean that all statements in the BatchExecuteStatement
/// succeeded. Error details for individual statements can be found under the Error
/// field of the BatchStatementResponse for each statement.
///
///
///
/// Container for the necessary parameters to execute the BatchExecuteStatement service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the BatchExecuteStatement service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
/// REST API Reference for BatchExecuteStatement Operation
public virtual Task BatchExecuteStatementAsync(BatchExecuteStatementRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = BatchExecuteStatementRequestMarshaller.Instance;
options.ResponseUnmarshaller = BatchExecuteStatementResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region BatchGetItem
internal virtual BatchGetItemResponse BatchGetItem(BatchGetItemRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = BatchGetItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = BatchGetItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = BatchGetItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// The BatchGetItem operation returns the attributes of one or more items
/// from one or more tables. You identify requested items by primary key.
///
///
///
/// A single operation can retrieve up to 16 MB of data, which can contain as many as
/// 100 items. BatchGetItem returns a partial result if the response size
/// limit is exceeded, the table's provisioned throughput is exceeded, more than 1MB per
/// partition is requested, or an internal processing failure occurs. If a partial result
/// is returned, the operation returns a value for UnprocessedKeys. You can
/// use this value to retry the operation starting with the next item to get.
///
///
///
/// If you request more than 100 items, BatchGetItem returns a ValidationException
/// with the message "Too many items requested for the BatchGetItem call."
///
///
///
/// For example, if you ask to retrieve 100 items, but each individual item is 300 KB
/// in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also
/// returns an appropriate UnprocessedKeys value so you can get the next
/// page of results. If desired, your application can include its own logic to assemble
/// the pages of results into one dataset.
///
///
///
/// If none of the items can be processed due to insufficient provisioned throughput
/// on all of the tables in the request, then BatchGetItem returns a ProvisionedThroughputExceededException.
/// If at least one of the items is successfully processed, then BatchGetItem
/// completes successfully, while returning the keys of the unread items in UnprocessedKeys.
///
///
///
/// If DynamoDB returns any unprocessed items, you should retry the batch operation on
/// those items. However, we strongly recommend that you use an exponential backoff
/// algorithm. If you retry the batch operation immediately, the underlying read or
/// write requests can still fail due to throttling on the individual tables. If you delay
/// the batch operation using exponential backoff, the individual requests in the batch
/// are much more likely to succeed.
///
///
///
/// For more information, see Batch
/// Operations and Error Handling in the Amazon DynamoDB Developer Guide.
///
///
///
/// By default, BatchGetItem performs eventually consistent reads on every
/// table in the request. If you want strongly consistent reads instead, you can set ConsistentRead
/// to true for any or all tables.
///
///
///
/// In order to minimize response latency, BatchGetItem may retrieve items
/// in parallel.
///
///
///
/// When designing your application, keep in mind that DynamoDB does not return items
/// in any particular order. To help parse the response by item, include the primary key
/// values for the items in your request in the ProjectionExpression parameter.
///
///
///
/// If a requested item does not exist, it is not returned in the result. Requests for
/// nonexistent items consume the minimum read capacity units according to the type of
/// read. For more information, see Working
/// with Tables in the Amazon DynamoDB Developer Guide.
///
///
/// A map of one or more table names and, for each table, a map that describes one or more items to retrieve from that table. Each table name can be used only once per BatchGetItem request. Each element in the map of items to retrieve consists of the following: -
ConsistentRead - If true, a strongly consistent read is used; if false (the default), an eventually consistent read is used. -
ExpressionAttributeNames - One or more substitution tokens for attribute names in the ProjectionExpression parameter. The following are some use cases for using ExpressionAttributeNames: - To access an attribute whose name conflicts with a DynamoDB reserved word.
- To create a placeholder for repeating occurrences of an attribute name in an expression.
- To prevent special characters in an attribute name from being misinterpreted in an expression.
Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: You could then use this substitution in an expression, as in this example: Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information about expression attribute names, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide. -
Keys - An array of primary key attribute values that define specific items in the table. For each primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide the partition key value. For a composite key, you must provide both the partition key value and the sort key value. -
ProjectionExpression - A string that identifies one or more attributes to retrieve from the table. These attributes can include scalars, sets, or elements of a JSON document. The attributes in the expression must be separated by commas. If no attribute names are specified, then all attributes are returned. If any of the requested attributes are not found, they do not appear in the result. For more information, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide. -
AttributesToGet - This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
/// A property of BatchGetItemRequest used to execute the BatchGetItem service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the BatchGetItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for BatchGetItem Operation
public virtual Task BatchGetItemAsync(Dictionary requestItems, ReturnConsumedCapacity returnConsumedCapacity, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new BatchGetItemRequest();
request.RequestItems = requestItems;
request.ReturnConsumedCapacity = returnConsumedCapacity;
return BatchGetItemAsync(request, cancellationToken);
}
///
/// The BatchGetItem operation returns the attributes of one or more items
/// from one or more tables. You identify requested items by primary key.
///
///
///
/// A single operation can retrieve up to 16 MB of data, which can contain as many as
/// 100 items. BatchGetItem returns a partial result if the response size
/// limit is exceeded, the table's provisioned throughput is exceeded, more than 1MB per
/// partition is requested, or an internal processing failure occurs. If a partial result
/// is returned, the operation returns a value for UnprocessedKeys. You can
/// use this value to retry the operation starting with the next item to get.
///
///
///
/// If you request more than 100 items, BatchGetItem returns a ValidationException
/// with the message "Too many items requested for the BatchGetItem call."
///
///
///
/// For example, if you ask to retrieve 100 items, but each individual item is 300 KB
/// in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also
/// returns an appropriate UnprocessedKeys value so you can get the next
/// page of results. If desired, your application can include its own logic to assemble
/// the pages of results into one dataset.
///
///
///
/// If none of the items can be processed due to insufficient provisioned throughput
/// on all of the tables in the request, then BatchGetItem returns a ProvisionedThroughputExceededException.
/// If at least one of the items is successfully processed, then BatchGetItem
/// completes successfully, while returning the keys of the unread items in UnprocessedKeys.
///
///
///
/// If DynamoDB returns any unprocessed items, you should retry the batch operation on
/// those items. However, we strongly recommend that you use an exponential backoff
/// algorithm. If you retry the batch operation immediately, the underlying read or
/// write requests can still fail due to throttling on the individual tables. If you delay
/// the batch operation using exponential backoff, the individual requests in the batch
/// are much more likely to succeed.
///
///
///
/// For more information, see Batch
/// Operations and Error Handling in the Amazon DynamoDB Developer Guide.
///
///
///
/// By default, BatchGetItem performs eventually consistent reads on every
/// table in the request. If you want strongly consistent reads instead, you can set ConsistentRead
/// to true for any or all tables.
///
///
///
/// In order to minimize response latency, BatchGetItem may retrieve items
/// in parallel.
///
///
///
/// When designing your application, keep in mind that DynamoDB does not return items
/// in any particular order. To help parse the response by item, include the primary key
/// values for the items in your request in the ProjectionExpression parameter.
///
///
///
/// If a requested item does not exist, it is not returned in the result. Requests for
/// nonexistent items consume the minimum read capacity units according to the type of
/// read. For more information, see Working
/// with Tables in the Amazon DynamoDB Developer Guide.
///
///
/// A map of one or more table names and, for each table, a map that describes one or more items to retrieve from that table. Each table name can be used only once per BatchGetItem request. Each element in the map of items to retrieve consists of the following: -
ConsistentRead - If true, a strongly consistent read is used; if false (the default), an eventually consistent read is used. -
ExpressionAttributeNames - One or more substitution tokens for attribute names in the ProjectionExpression parameter. The following are some use cases for using ExpressionAttributeNames: - To access an attribute whose name conflicts with a DynamoDB reserved word.
- To create a placeholder for repeating occurrences of an attribute name in an expression.
- To prevent special characters in an attribute name from being misinterpreted in an expression.
Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: You could then use this substitution in an expression, as in this example: Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information about expression attribute names, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide. -
Keys - An array of primary key attribute values that define specific items in the table. For each primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide the partition key value. For a composite key, you must provide both the partition key value and the sort key value. -
ProjectionExpression - A string that identifies one or more attributes to retrieve from the table. These attributes can include scalars, sets, or elements of a JSON document. The attributes in the expression must be separated by commas. If no attribute names are specified, then all attributes are returned. If any of the requested attributes are not found, they do not appear in the result. For more information, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide. -
AttributesToGet - This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the BatchGetItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for BatchGetItem Operation
public virtual Task BatchGetItemAsync(Dictionary requestItems, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new BatchGetItemRequest();
request.RequestItems = requestItems;
return BatchGetItemAsync(request, cancellationToken);
}
///
/// The BatchGetItem operation returns the attributes of one or more items
/// from one or more tables. You identify requested items by primary key.
///
///
///
/// A single operation can retrieve up to 16 MB of data, which can contain as many as
/// 100 items. BatchGetItem returns a partial result if the response size
/// limit is exceeded, the table's provisioned throughput is exceeded, more than 1MB per
/// partition is requested, or an internal processing failure occurs. If a partial result
/// is returned, the operation returns a value for UnprocessedKeys. You can
/// use this value to retry the operation starting with the next item to get.
///
///
///
/// If you request more than 100 items, BatchGetItem returns a ValidationException
/// with the message "Too many items requested for the BatchGetItem call."
///
///
///
/// For example, if you ask to retrieve 100 items, but each individual item is 300 KB
/// in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also
/// returns an appropriate UnprocessedKeys value so you can get the next
/// page of results. If desired, your application can include its own logic to assemble
/// the pages of results into one dataset.
///
///
///
/// If none of the items can be processed due to insufficient provisioned throughput
/// on all of the tables in the request, then BatchGetItem returns a ProvisionedThroughputExceededException.
/// If at least one of the items is successfully processed, then BatchGetItem
/// completes successfully, while returning the keys of the unread items in UnprocessedKeys.
///
///
///
/// If DynamoDB returns any unprocessed items, you should retry the batch operation on
/// those items. However, we strongly recommend that you use an exponential backoff
/// algorithm. If you retry the batch operation immediately, the underlying read or
/// write requests can still fail due to throttling on the individual tables. If you delay
/// the batch operation using exponential backoff, the individual requests in the batch
/// are much more likely to succeed.
///
///
///
/// For more information, see Batch
/// Operations and Error Handling in the Amazon DynamoDB Developer Guide.
///
///
///
/// By default, BatchGetItem performs eventually consistent reads on every
/// table in the request. If you want strongly consistent reads instead, you can set ConsistentRead
/// to true for any or all tables.
///
///
///
/// In order to minimize response latency, BatchGetItem may retrieve items
/// in parallel.
///
///
///
/// When designing your application, keep in mind that DynamoDB does not return items
/// in any particular order. To help parse the response by item, include the primary key
/// values for the items in your request in the ProjectionExpression parameter.
///
///
///
/// If a requested item does not exist, it is not returned in the result. Requests for
/// nonexistent items consume the minimum read capacity units according to the type of
/// read. For more information, see Working
/// with Tables in the Amazon DynamoDB Developer Guide.
///
///
/// Container for the necessary parameters to execute the BatchGetItem service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the BatchGetItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for BatchGetItem Operation
public virtual Task BatchGetItemAsync(BatchGetItemRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = BatchGetItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = BatchGetItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = BatchGetItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region BatchWriteItem
internal virtual BatchWriteItemResponse BatchWriteItem(BatchWriteItemRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = BatchWriteItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = BatchWriteItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = BatchWriteItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// The BatchWriteItem operation puts or deletes multiple items in one or
/// more tables. A single call to BatchWriteItem can transmit up to 16MB
/// of data over the network, consisting of up to 25 item put or delete operations. While
/// individual items can be up to 400 KB once stored, it's important to note that an item's
/// representation might be greater than 400KB while being sent in DynamoDB's JSON format
/// for the API call. For more details on this distinction, see Naming
/// Rules and Data Types.
///
///
///
/// BatchWriteItem cannot update items. If you perform a BatchWriteItem
/// operation on an existing item, that item's values will be overwritten by the operation
/// and it will appear like it was updated. To update items, we recommend you use the
/// UpdateItem action.
///
///
///
/// The individual PutItem and DeleteItem operations specified
/// in BatchWriteItem are atomic; however BatchWriteItem as
/// a whole is not. If any requested operations fail because the table's provisioned throughput
/// is exceeded or an internal processing failure occurs, the failed operations are returned
/// in the UnprocessedItems response parameter. You can investigate and optionally
/// resend the requests. Typically, you would call BatchWriteItem in a loop.
/// Each iteration would check for unprocessed items and submit a new BatchWriteItem
/// request with those unprocessed items until all items have been processed.
///
///
///
/// If none of the items can be processed due to insufficient provisioned throughput
/// on all of the tables in the request, then BatchWriteItem returns a ProvisionedThroughputExceededException.
///
///
///
/// If DynamoDB returns any unprocessed items, you should retry the batch operation on
/// those items. However, we strongly recommend that you use an exponential backoff
/// algorithm. If you retry the batch operation immediately, the underlying read or
/// write requests can still fail due to throttling on the individual tables. If you delay
/// the batch operation using exponential backoff, the individual requests in the batch
/// are much more likely to succeed.
///
///
///
/// For more information, see Batch
/// Operations and Error Handling in the Amazon DynamoDB Developer Guide.
///
///
///
/// With BatchWriteItem, you can efficiently write or delete large amounts
/// of data, such as from Amazon EMR, or copy data from another database into DynamoDB.
/// In order to improve performance with these large-scale operations, BatchWriteItem
/// does not behave in the same way as individual PutItem and DeleteItem
/// calls would. For example, you cannot specify conditions on individual put and delete
/// requests, and BatchWriteItem does not return deleted items in the response.
///
///
///
/// If you use a programming language that supports concurrency, you can use threads to
/// write items in parallel. Your application must include the necessary logic to manage
/// the threads. With languages that don't support threading, you must update or delete
/// the specified items one at a time. In both situations, BatchWriteItem
/// performs the specified put and delete operations in parallel, giving you the power
/// of the thread pool approach without having to introduce complexity into your application.
///
///
///
/// Parallel processing reduces latency, but each specified put and delete request consumes
/// the same number of write capacity units whether it is processed in parallel or not.
/// Delete operations on nonexistent items consume one write capacity unit.
///
///
///
/// If one or more of the following is true, DynamoDB rejects the entire batch write operation:
///
/// -
///
/// One or more tables specified in the
BatchWriteItem request does not exist.
///
/// -
///
/// Primary key attributes specified on an item in the request do not match those in the
/// corresponding table's primary key schema.
///
///
-
///
/// You try to perform multiple operations on the same item in the same
BatchWriteItem
/// request. For example, you cannot put and delete the same item in the same BatchWriteItem
/// request.
///
/// -
///
/// Your request contains at least two items with identical hash and range keys (which
/// essentially is two put operations).
///
///
-
///
/// There are more than 25 requests in the batch.
///
///
-
///
/// Any individual item in a batch exceeds 400 KB.
///
///
-
///
/// The total request size exceeds 16 MB.
///
///
///
/// A map of one or more table names and, for each table, a list of operations to be performed (DeleteRequest or PutRequest). Each element in the map consists of the following: -
DeleteRequest - Perform a DeleteItem operation on the specified item. The item to be deleted is identified by a Key subelement: -
Key - A map of primary key attribute values that uniquely identify the item. Each entry in this map consists of an attribute name and an attribute value. For each primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
-
PutRequest - Perform a PutItem operation on the specified item. The item to be put is identified by an Item subelement: -
Item - A map of attributes and their values. Each entry in this map consists of an attribute name and an attribute value. Attribute values must not be null; string and binary type attributes must have lengths greater than zero; and set type attributes must not be empty. Requests that contain empty values are rejected with a ValidationException exception. If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the BatchWriteItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for BatchWriteItem Operation
public virtual Task BatchWriteItemAsync(Dictionary> requestItems, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new BatchWriteItemRequest();
request.RequestItems = requestItems;
return BatchWriteItemAsync(request, cancellationToken);
}
///
/// The BatchWriteItem operation puts or deletes multiple items in one or
/// more tables. A single call to BatchWriteItem can transmit up to 16MB
/// of data over the network, consisting of up to 25 item put or delete operations. While
/// individual items can be up to 400 KB once stored, it's important to note that an item's
/// representation might be greater than 400KB while being sent in DynamoDB's JSON format
/// for the API call. For more details on this distinction, see Naming
/// Rules and Data Types.
///
///
///
/// BatchWriteItem cannot update items. If you perform a BatchWriteItem
/// operation on an existing item, that item's values will be overwritten by the operation
/// and it will appear like it was updated. To update items, we recommend you use the
/// UpdateItem action.
///
///
///
/// The individual PutItem and DeleteItem operations specified
/// in BatchWriteItem are atomic; however BatchWriteItem as
/// a whole is not. If any requested operations fail because the table's provisioned throughput
/// is exceeded or an internal processing failure occurs, the failed operations are returned
/// in the UnprocessedItems response parameter. You can investigate and optionally
/// resend the requests. Typically, you would call BatchWriteItem in a loop.
/// Each iteration would check for unprocessed items and submit a new BatchWriteItem
/// request with those unprocessed items until all items have been processed.
///
///
///
/// If none of the items can be processed due to insufficient provisioned throughput
/// on all of the tables in the request, then BatchWriteItem returns a ProvisionedThroughputExceededException.
///
///
///
/// If DynamoDB returns any unprocessed items, you should retry the batch operation on
/// those items. However, we strongly recommend that you use an exponential backoff
/// algorithm. If you retry the batch operation immediately, the underlying read or
/// write requests can still fail due to throttling on the individual tables. If you delay
/// the batch operation using exponential backoff, the individual requests in the batch
/// are much more likely to succeed.
///
///
///
/// For more information, see Batch
/// Operations and Error Handling in the Amazon DynamoDB Developer Guide.
///
///
///
/// With BatchWriteItem, you can efficiently write or delete large amounts
/// of data, such as from Amazon EMR, or copy data from another database into DynamoDB.
/// In order to improve performance with these large-scale operations, BatchWriteItem
/// does not behave in the same way as individual PutItem and DeleteItem
/// calls would. For example, you cannot specify conditions on individual put and delete
/// requests, and BatchWriteItem does not return deleted items in the response.
///
///
///
/// If you use a programming language that supports concurrency, you can use threads to
/// write items in parallel. Your application must include the necessary logic to manage
/// the threads. With languages that don't support threading, you must update or delete
/// the specified items one at a time. In both situations, BatchWriteItem
/// performs the specified put and delete operations in parallel, giving you the power
/// of the thread pool approach without having to introduce complexity into your application.
///
///
///
/// Parallel processing reduces latency, but each specified put and delete request consumes
/// the same number of write capacity units whether it is processed in parallel or not.
/// Delete operations on nonexistent items consume one write capacity unit.
///
///
///
/// If one or more of the following is true, DynamoDB rejects the entire batch write operation:
///
/// -
///
/// One or more tables specified in the
BatchWriteItem request does not exist.
///
/// -
///
/// Primary key attributes specified on an item in the request do not match those in the
/// corresponding table's primary key schema.
///
///
-
///
/// You try to perform multiple operations on the same item in the same
BatchWriteItem
/// request. For example, you cannot put and delete the same item in the same BatchWriteItem
/// request.
///
/// -
///
/// Your request contains at least two items with identical hash and range keys (which
/// essentially is two put operations).
///
///
-
///
/// There are more than 25 requests in the batch.
///
///
-
///
/// Any individual item in a batch exceeds 400 KB.
///
///
-
///
/// The total request size exceeds 16 MB.
///
///
///
/// Container for the necessary parameters to execute the BatchWriteItem service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the BatchWriteItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for BatchWriteItem Operation
public virtual Task BatchWriteItemAsync(BatchWriteItemRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = BatchWriteItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = BatchWriteItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = BatchWriteItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region CreateBackup
internal virtual CreateBackupResponse CreateBackup(CreateBackupRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = CreateBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = CreateBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = CreateBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Creates a backup for an existing table.
///
///
///
/// Each time you create an on-demand backup, the entire table data is backed up. There
/// is no limit to the number of on-demand backups that can be taken.
///
///
///
/// When you create an on-demand backup, a time marker of the request is cataloged, and
/// the backup is created asynchronously, by applying all changes until the time of the
/// request to the last full table snapshot. Backup requests are processed instantaneously
/// and become available for restore within minutes.
///
///
///
/// You can call CreateBackup at a maximum rate of 50 times per second.
///
///
///
/// All backups in DynamoDB work without consuming any provisioned throughput on the table.
///
///
///
/// If you submit a backup request on 2018-12-14 at 14:25:00, the backup is guaranteed
/// to contain all data committed to the table up to 14:24:00, and data committed after
/// 14:26:00 will not be. The backup might contain data modifications made between 14:24:00
/// and 14:26:00. On-demand backup does not support causal consistency.
///
///
///
/// Along with data, the following are also included on the backups:
///
/// -
///
/// Global secondary indexes (GSIs)
///
///
-
///
/// Local secondary indexes (LSIs)
///
///
-
///
/// Streams
///
///
-
///
/// Provisioned read and write capacity
///
///
///
/// Container for the necessary parameters to execute the CreateBackup service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the CreateBackup service method, as returned by DynamoDB.
///
/// There is another ongoing conflicting backup control plane operation on the table.
/// The backup is either being created, deleted or restored to a table.
///
///
/// Backups have not yet been enabled for this table.
///
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// A target table with the specified name is either being created or deleted.
///
///
/// A source table with the name TableName does not currently exist within
/// the subscriber's account or the subscriber is operating in the wrong Amazon Web Services
/// Region.
///
/// REST API Reference for CreateBackup Operation
public virtual Task CreateBackupAsync(CreateBackupRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = CreateBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = CreateBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = CreateBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region CreateGlobalTable
internal virtual CreateGlobalTableResponse CreateGlobalTable(CreateGlobalTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = CreateGlobalTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = CreateGlobalTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = CreateGlobalTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Creates a global table from an existing table. A global table creates a replication
/// relationship between two or more DynamoDB tables with the same table name in the provided
/// Regions.
///
///
///
/// This operation only applies to Version
/// 2017.11.29 (Legacy) of global tables. We recommend using Version
/// 2019.11.21 (Current) when creating new global tables, as it provides greater flexibility,
/// higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine
/// which version you are using, see Determining
/// the version. To update existing global tables from version 2017.11.29 (Legacy)
/// to version 2019.11.21 (Current), see
/// Updating global tables.
///
///
///
/// If you want to add a new replica table to a global table, each of the following conditions
/// must be true:
///
/// -
///
/// The table must have the same primary key as all of the other replicas.
///
///
-
///
/// The table must have the same name as all of the other replicas.
///
///
-
///
/// The table must have DynamoDB Streams enabled, with the stream containing both the
/// new and the old images of the item.
///
///
-
///
/// None of the replica tables in the global table can contain any data.
///
///
///
/// If global secondary indexes are specified, then the following conditions must also
/// be met:
///
/// -
///
/// The global secondary indexes must have the same name.
///
///
-
///
/// The global secondary indexes must have the same hash key and sort key (if present).
///
///
///
///
/// If local secondary indexes are specified, then the following conditions must also
/// be met:
///
/// -
///
/// The local secondary indexes must have the same name.
///
///
-
///
/// The local secondary indexes must have the same hash key and sort key (if present).
///
///
///
///
/// Write capacity settings should be set consistently across your replica tables and
/// secondary indexes. DynamoDB strongly recommends enabling auto scaling to manage the
/// write capacity settings for all of your global tables replicas and indexes.
///
///
///
/// If you prefer to manage write capacity settings manually, you should provision equal
/// replicated write capacity units to your replica tables. You should also provision
/// equal replicated write capacity units to matching secondary indexes across your global
/// table.
///
///
///
/// Container for the necessary parameters to execute the CreateGlobalTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the CreateGlobalTable service method, as returned by DynamoDB.
///
/// The specified global table already exists.
///
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// A source table with the name TableName does not currently exist within
/// the subscriber's account or the subscriber is operating in the wrong Amazon Web Services
/// Region.
///
/// REST API Reference for CreateGlobalTable Operation
public virtual Task CreateGlobalTableAsync(CreateGlobalTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = CreateGlobalTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = CreateGlobalTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = CreateGlobalTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region CreateTable
internal virtual CreateTableResponse CreateTable(CreateTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = CreateTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = CreateTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = CreateTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// The CreateTable operation adds a new table to your account. In an Amazon
/// Web Services account, table names must be unique within each Region. That is, you
/// can have two tables with same name if you create the tables in different Regions.
///
///
///
/// CreateTable is an asynchronous operation. Upon receiving a CreateTable
/// request, DynamoDB immediately returns a response with a TableStatus of
/// CREATING. After the table is created, DynamoDB sets the TableStatus
/// to ACTIVE. You can perform read and write operations only on an ACTIVE
/// table.
///
///
///
/// You can optionally define secondary indexes on the new table, as part of the CreateTable
/// operation. If you want to create multiple tables with secondary indexes on them, you
/// must create the tables sequentially. Only one table with secondary indexes can be
/// in the CREATING state at any given time.
///
///
///
/// You can use the DescribeTable action to check the table status.
///
///
/// The name of the table to create.
/// Specifies the attributes that make up the primary key for a table or an index. The attributes in KeySchema must also be defined in the AttributeDefinitions array. For more information, see Data Model in the Amazon DynamoDB Developer Guide. Each KeySchemaElement in the array is composed of: -
AttributeName - The name of this key attribute. -
KeyType - The role that the key attribute will assume: -
HASH - partition key -
RANGE - sort key
The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from the DynamoDB usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value. For a simple primary key (partition key), you must provide exactly one element with a KeyType of HASH. For a composite primary key (partition key and sort key), you must provide exactly two elements, in this order: The first element must have a KeyType of HASH, and the second element must have a KeyType of RANGE. For more information, see Working with Tables in the Amazon DynamoDB Developer Guide.
/// An array of attributes that describe the key schema for the table and indexes.
/// Represents the provisioned throughput settings for a specified table or index. The settings can be modified using the UpdateTable operation. If you set BillingMode as PROVISIONED, you must specify this property. If you set BillingMode as PAY_PER_REQUEST, you cannot specify this property. For current minimum and maximum provisioned throughput values, see Service, Account, and Table Quotas in the Amazon DynamoDB Developer Guide.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the CreateTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
/// REST API Reference for CreateTable Operation
public virtual Task CreateTableAsync(string tableName, List keySchema, List attributeDefinitions, ProvisionedThroughput provisionedThroughput, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new CreateTableRequest();
request.TableName = tableName;
request.KeySchema = keySchema;
request.AttributeDefinitions = attributeDefinitions;
request.ProvisionedThroughput = provisionedThroughput;
return CreateTableAsync(request, cancellationToken);
}
///
/// The CreateTable operation adds a new table to your account. In an Amazon
/// Web Services account, table names must be unique within each Region. That is, you
/// can have two tables with same name if you create the tables in different Regions.
///
///
///
/// CreateTable is an asynchronous operation. Upon receiving a CreateTable
/// request, DynamoDB immediately returns a response with a TableStatus of
/// CREATING. After the table is created, DynamoDB sets the TableStatus
/// to ACTIVE. You can perform read and write operations only on an ACTIVE
/// table.
///
///
///
/// You can optionally define secondary indexes on the new table, as part of the CreateTable
/// operation. If you want to create multiple tables with secondary indexes on them, you
/// must create the tables sequentially. Only one table with secondary indexes can be
/// in the CREATING state at any given time.
///
///
///
/// You can use the DescribeTable action to check the table status.
///
///
/// Container for the necessary parameters to execute the CreateTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the CreateTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
/// REST API Reference for CreateTable Operation
public virtual Task CreateTableAsync(CreateTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = CreateTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = CreateTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = CreateTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DeleteBackup
internal virtual DeleteBackupResponse DeleteBackup(DeleteBackupRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DeleteBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = DeleteBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DeleteBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Deletes an existing backup of a table.
///
///
///
/// You can call DeleteBackup at a maximum rate of 10 times per second.
///
///
/// Container for the necessary parameters to execute the DeleteBackup service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DeleteBackup service method, as returned by DynamoDB.
///
/// There is another ongoing conflicting backup control plane operation on the table.
/// The backup is either being created, deleted or restored to a table.
///
///
/// Backup not found for the given BackupARN.
///
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
/// REST API Reference for DeleteBackup Operation
public virtual Task DeleteBackupAsync(DeleteBackupRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DeleteBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = DeleteBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DeleteBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DeleteItem
internal virtual DeleteItemResponse DeleteItem(DeleteItemRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DeleteItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = DeleteItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DeleteItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Deletes a single item in a table by primary key. You can perform a conditional delete
/// operation that deletes the item if it exists, or if it has an expected attribute value.
///
///
///
/// In addition to deleting an item, you can also return the item's attribute values in
/// the same operation, using the ReturnValues parameter.
///
///
///
/// Unless you specify conditions, the DeleteItem is an idempotent operation;
/// running it multiple times on the same item or attribute does not result in
/// an error response.
///
///
///
/// Conditional deletes are useful for deleting items only if specific conditions are
/// met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item
/// is not deleted.
///
///
/// The name of the table from which to delete the item.
/// A map of attribute names to AttributeValue objects, representing the primary key of the item to delete. For the primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DeleteItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for DeleteItem Operation
public virtual Task DeleteItemAsync(string tableName, Dictionary key, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new DeleteItemRequest();
request.TableName = tableName;
request.Key = key;
return DeleteItemAsync(request, cancellationToken);
}
///
/// Deletes a single item in a table by primary key. You can perform a conditional delete
/// operation that deletes the item if it exists, or if it has an expected attribute value.
///
///
///
/// In addition to deleting an item, you can also return the item's attribute values in
/// the same operation, using the ReturnValues parameter.
///
///
///
/// Unless you specify conditions, the DeleteItem is an idempotent operation;
/// running it multiple times on the same item or attribute does not result in
/// an error response.
///
///
///
/// Conditional deletes are useful for deleting items only if specific conditions are
/// met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item
/// is not deleted.
///
///
/// The name of the table from which to delete the item.
/// A map of attribute names to AttributeValue objects, representing the primary key of the item to delete. For the primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
/// Use ReturnValues if you want to get the item attributes as they appeared before they were deleted. For DeleteItem, the valid values are: -
NONE - If ReturnValues is not specified, or if its value is NONE, then nothing is returned. (This setting is the default for ReturnValues.) -
ALL_OLD - The content of the old item is returned.
There is no additional cost associated with requesting a return value aside from the small network and processing overhead of receiving a larger response. No read capacity units are consumed. The ReturnValues parameter is used by several DynamoDB operations; however, DeleteItem does not recognize any values other than NONE or ALL_OLD.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DeleteItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for DeleteItem Operation
public virtual Task DeleteItemAsync(string tableName, Dictionary key, ReturnValue returnValues, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new DeleteItemRequest();
request.TableName = tableName;
request.Key = key;
request.ReturnValues = returnValues;
return DeleteItemAsync(request, cancellationToken);
}
///
/// Deletes a single item in a table by primary key. You can perform a conditional delete
/// operation that deletes the item if it exists, or if it has an expected attribute value.
///
///
///
/// In addition to deleting an item, you can also return the item's attribute values in
/// the same operation, using the ReturnValues parameter.
///
///
///
/// Unless you specify conditions, the DeleteItem is an idempotent operation;
/// running it multiple times on the same item or attribute does not result in
/// an error response.
///
///
///
/// Conditional deletes are useful for deleting items only if specific conditions are
/// met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item
/// is not deleted.
///
///
/// Container for the necessary parameters to execute the DeleteItem service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DeleteItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for DeleteItem Operation
public virtual Task DeleteItemAsync(DeleteItemRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DeleteItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = DeleteItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DeleteItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DeleteTable
internal virtual DeleteTableResponse DeleteTable(DeleteTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DeleteTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = DeleteTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DeleteTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// The DeleteTable operation deletes a table and all of its items. After
/// a DeleteTable request, the specified table is in the DELETING
/// state until DynamoDB completes the deletion. If the table is in the ACTIVE
/// state, you can delete it. If a table is in CREATING or UPDATING
/// states, then DynamoDB returns a ResourceInUseException. If the specified
/// table does not exist, DynamoDB returns a ResourceNotFoundException. If
/// table is already in the DELETING state, no error is returned.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// DynamoDB might continue to accept data read and write operations, such as GetItem
/// and PutItem, on a table in the DELETING state until the
/// table deletion is complete.
///
///
///
/// When you delete a table, any indexes on that table are also deleted.
///
///
///
/// If you have DynamoDB Streams enabled on the table, then the corresponding stream on
/// that table goes into the DISABLED state, and the stream is automatically
/// deleted after 24 hours.
///
///
///
/// Use the DescribeTable action to check the status of the table.
///
///
/// The name of the table to delete.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DeleteTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DeleteTable Operation
public virtual Task DeleteTableAsync(string tableName, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new DeleteTableRequest();
request.TableName = tableName;
return DeleteTableAsync(request, cancellationToken);
}
///
/// The DeleteTable operation deletes a table and all of its items. After
/// a DeleteTable request, the specified table is in the DELETING
/// state until DynamoDB completes the deletion. If the table is in the ACTIVE
/// state, you can delete it. If a table is in CREATING or UPDATING
/// states, then DynamoDB returns a ResourceInUseException. If the specified
/// table does not exist, DynamoDB returns a ResourceNotFoundException. If
/// table is already in the DELETING state, no error is returned.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// DynamoDB might continue to accept data read and write operations, such as GetItem
/// and PutItem, on a table in the DELETING state until the
/// table deletion is complete.
///
///
///
/// When you delete a table, any indexes on that table are also deleted.
///
///
///
/// If you have DynamoDB Streams enabled on the table, then the corresponding stream on
/// that table goes into the DISABLED state, and the stream is automatically
/// deleted after 24 hours.
///
///
///
/// Use the DescribeTable action to check the status of the table.
///
///
/// Container for the necessary parameters to execute the DeleteTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DeleteTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DeleteTable Operation
public virtual Task DeleteTableAsync(DeleteTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DeleteTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = DeleteTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DeleteTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeBackup
internal virtual DescribeBackupResponse DescribeBackup(DescribeBackupRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Describes an existing backup of a table.
///
///
///
/// You can call DescribeBackup at a maximum rate of 10 times per second.
///
///
/// Container for the necessary parameters to execute the DescribeBackup service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeBackup service method, as returned by DynamoDB.
///
/// Backup not found for the given BackupARN.
///
///
/// An error occurred on the server side.
///
/// REST API Reference for DescribeBackup Operation
public virtual Task DescribeBackupAsync(DescribeBackupRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeContinuousBackups
internal virtual DescribeContinuousBackupsResponse DescribeContinuousBackups(DescribeContinuousBackupsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeContinuousBackupsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeContinuousBackupsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeContinuousBackupsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Checks the status of continuous backups and point in time recovery on the specified
/// table. Continuous backups are ENABLED on all tables at table creation.
/// If point in time recovery is enabled, PointInTimeRecoveryStatus will
/// be set to ENABLED.
///
///
///
/// After continuous backups and point in time recovery are enabled, you can restore
/// to any point in time within EarliestRestorableDateTime and LatestRestorableDateTime.
///
///
///
///
/// LatestRestorableDateTime is typically 5 minutes before the current time.
/// You can restore your table to any point in time during the last 35 days.
///
///
///
/// You can call DescribeContinuousBackups at a maximum rate of 10 times
/// per second.
///
///
/// Container for the necessary parameters to execute the DescribeContinuousBackups service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeContinuousBackups service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// A source table with the name TableName does not currently exist within
/// the subscriber's account or the subscriber is operating in the wrong Amazon Web Services
/// Region.
///
/// REST API Reference for DescribeContinuousBackups Operation
public virtual Task DescribeContinuousBackupsAsync(DescribeContinuousBackupsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeContinuousBackupsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeContinuousBackupsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeContinuousBackupsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeContributorInsights
internal virtual DescribeContributorInsightsResponse DescribeContributorInsights(DescribeContributorInsightsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeContributorInsightsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeContributorInsightsResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Returns information about contributor insights for a given table or global secondary
/// index.
///
/// Container for the necessary parameters to execute the DescribeContributorInsights service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeContributorInsights service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DescribeContributorInsights Operation
public virtual Task DescribeContributorInsightsAsync(DescribeContributorInsightsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeContributorInsightsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeContributorInsightsResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeEndpoints
internal virtual DescribeEndpointsResponse DescribeEndpoints(DescribeEndpointsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeEndpointsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeEndpointsResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Returns the regional endpoint information. For more information on policy permissions,
/// please see Internetwork
/// traffic privacy.
///
/// Container for the necessary parameters to execute the DescribeEndpoints service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeEndpoints service method, as returned by DynamoDB.
/// REST API Reference for DescribeEndpoints Operation
public virtual Task DescribeEndpointsAsync(DescribeEndpointsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeEndpointsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeEndpointsResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeExport
internal virtual DescribeExportResponse DescribeExport(DescribeExportRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeExportRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeExportResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Describes an existing table export.
///
/// Container for the necessary parameters to execute the DescribeExport service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeExport service method, as returned by DynamoDB.
///
/// The specified export was not found.
///
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
/// REST API Reference for DescribeExport Operation
public virtual Task DescribeExportAsync(DescribeExportRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeExportRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeExportResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeGlobalTable
internal virtual DescribeGlobalTableResponse DescribeGlobalTable(DescribeGlobalTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeGlobalTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeGlobalTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeGlobalTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Returns information about the specified global table.
///
///
///
/// This operation only applies to Version
/// 2017.11.29 (Legacy) of global tables. We recommend using Version
/// 2019.11.21 (Current) when creating new global tables, as it provides greater flexibility,
/// higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine
/// which version you are using, see Determining
/// the version. To update existing global tables from version 2017.11.29 (Legacy)
/// to version 2019.11.21 (Current), see
/// Updating global tables.
///
///
///
/// Container for the necessary parameters to execute the DescribeGlobalTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeGlobalTable service method, as returned by DynamoDB.
///
/// The specified global table does not exist.
///
///
/// An error occurred on the server side.
///
/// REST API Reference for DescribeGlobalTable Operation
public virtual Task DescribeGlobalTableAsync(DescribeGlobalTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeGlobalTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeGlobalTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeGlobalTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeGlobalTableSettings
internal virtual DescribeGlobalTableSettingsResponse DescribeGlobalTableSettings(DescribeGlobalTableSettingsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeGlobalTableSettingsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeGlobalTableSettingsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeGlobalTableSettingsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Describes Region-specific settings for a global table.
///
///
///
/// This operation only applies to Version
/// 2017.11.29 (Legacy) of global tables. We recommend using Version
/// 2019.11.21 (Current) when creating new global tables, as it provides greater flexibility,
/// higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine
/// which version you are using, see Determining
/// the version. To update existing global tables from version 2017.11.29 (Legacy)
/// to version 2019.11.21 (Current), see
/// Updating global tables.
///
///
///
/// Container for the necessary parameters to execute the DescribeGlobalTableSettings service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeGlobalTableSettings service method, as returned by DynamoDB.
///
/// The specified global table does not exist.
///
///
/// An error occurred on the server side.
///
/// REST API Reference for DescribeGlobalTableSettings Operation
public virtual Task DescribeGlobalTableSettingsAsync(DescribeGlobalTableSettingsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeGlobalTableSettingsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeGlobalTableSettingsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeGlobalTableSettingsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeImport
internal virtual DescribeImportResponse DescribeImport(DescribeImportRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeImportRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeImportResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Represents the properties of the import.
///
/// Container for the necessary parameters to execute the DescribeImport service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeImport service method, as returned by DynamoDB.
///
/// The specified import was not found.
///
/// REST API Reference for DescribeImport Operation
public virtual Task DescribeImportAsync(DescribeImportRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeImportRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeImportResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeKinesisStreamingDestination
internal virtual DescribeKinesisStreamingDestinationResponse DescribeKinesisStreamingDestination(DescribeKinesisStreamingDestinationRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeKinesisStreamingDestinationRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeKinesisStreamingDestinationResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeKinesisStreamingDestinationEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Returns information about the status of Kinesis streaming.
///
/// Container for the necessary parameters to execute the DescribeKinesisStreamingDestination service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeKinesisStreamingDestination service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DescribeKinesisStreamingDestination Operation
public virtual Task DescribeKinesisStreamingDestinationAsync(DescribeKinesisStreamingDestinationRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeKinesisStreamingDestinationRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeKinesisStreamingDestinationResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeKinesisStreamingDestinationEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeLimits
internal virtual DescribeLimitsResponse DescribeLimits(DescribeLimitsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeLimitsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeLimitsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeLimitsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Returns the current provisioned-capacity quotas for your Amazon Web Services account
/// in a Region, both for the Region as a whole and for any one DynamoDB table that you
/// create there.
///
///
///
/// When you establish an Amazon Web Services account, the account has initial quotas
/// on the maximum read capacity units and write capacity units that you can provision
/// across all of your DynamoDB tables in a given Region. Also, there are per-table quotas
/// that apply when you create a table there. For more information, see Service,
/// Account, and Table Quotas page in the Amazon DynamoDB Developer Guide.
///
///
///
/// Although you can increase these quotas by filing a case at Amazon
/// Web Services Support Center, obtaining the increase is not instantaneous. The
/// DescribeLimits action lets you write code to compare the capacity you
/// are currently using to those quotas imposed by your account so that you have enough
/// time to apply for an increase before you hit a quota.
///
///
///
/// For example, you could use one of the Amazon Web Services SDKs to do the following:
///
/// -
///
/// Call
DescribeLimits for a particular Region to obtain your current account
/// quotas on provisioned capacity there.
///
/// -
///
/// Create a variable to hold the aggregate read capacity units provisioned for all your
/// tables in that Region, and one to hold the aggregate write capacity units. Zero them
/// both.
///
///
-
///
/// Call
ListTables to obtain a list of all your DynamoDB tables.
///
/// -
///
/// For each table name listed by
ListTables, do the following:
///
/// -
///
/// Call
DescribeTable with the table name.
///
/// -
///
/// Use the data returned by
DescribeTable to add the read capacity units
/// and write capacity units provisioned for the table itself to your variables.
///
/// -
///
/// If the table has one or more global secondary indexes (GSIs), loop over these GSIs
/// and add their provisioned capacity values to your variables as well.
///
///
-
///
/// Report the account quotas for that Region returned by
DescribeLimits,
/// along with the total current provisioned capacity levels you have calculated.
///
///
///
/// This will let you see whether you are getting close to your account-level quotas.
///
///
///
/// The per-table quotas apply only when you are creating a new table. They restrict the
/// sum of the provisioned capacity of the new table itself and all its global secondary
/// indexes.
///
///
///
/// For existing tables and their GSIs, DynamoDB doesn't let you increase provisioned
/// capacity extremely rapidly, but the only quota that applies is that the aggregate
/// provisioned capacity over all your tables and GSIs cannot exceed either of the per-account
/// quotas.
///
///
///
/// DescribeLimits should only be called periodically. You can expect throttling
/// errors if you call it more than once in a minute.
///
///
///
/// The DescribeLimits Request element has no content.
///
///
/// Container for the necessary parameters to execute the DescribeLimits service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeLimits service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for DescribeLimits Operation
public virtual Task DescribeLimitsAsync(DescribeLimitsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeLimitsRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeLimitsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeLimitsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeTable
internal virtual DescribeTableResponse DescribeTable(DescribeTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Returns information about the table, including the current status of the table, when
/// it was created, the primary key schema, and any indexes on the table.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// If you issue a DescribeTable request immediately after a CreateTable
/// request, DynamoDB might return a ResourceNotFoundException. This is because
/// DescribeTable uses an eventually consistent query, and the metadata for
/// your table might not be available at that moment. Wait for a few seconds, and then
/// try the DescribeTable request again.
///
///
///
/// The name of the table to describe.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DescribeTable Operation
public virtual Task DescribeTableAsync(string tableName, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new DescribeTableRequest();
request.TableName = tableName;
return DescribeTableAsync(request, cancellationToken);
}
///
/// Returns information about the table, including the current status of the table, when
/// it was created, the primary key schema, and any indexes on the table.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// If you issue a DescribeTable request immediately after a CreateTable
/// request, DynamoDB might return a ResourceNotFoundException. This is because
/// DescribeTable uses an eventually consistent query, and the metadata for
/// your table might not be available at that moment. Wait for a few seconds, and then
/// try the DescribeTable request again.
///
///
///
/// Container for the necessary parameters to execute the DescribeTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DescribeTable Operation
public virtual Task DescribeTableAsync(DescribeTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeTableReplicaAutoScaling
internal virtual DescribeTableReplicaAutoScalingResponse DescribeTableReplicaAutoScaling(DescribeTableReplicaAutoScalingRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeTableReplicaAutoScalingRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeTableReplicaAutoScalingResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Describes auto scaling settings across replicas of the global table at once.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// Container for the necessary parameters to execute the DescribeTableReplicaAutoScaling service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeTableReplicaAutoScaling service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DescribeTableReplicaAutoScaling Operation
public virtual Task DescribeTableReplicaAutoScalingAsync(DescribeTableReplicaAutoScalingRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeTableReplicaAutoScalingRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeTableReplicaAutoScalingResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DescribeTimeToLive
internal virtual DescribeTimeToLiveResponse DescribeTimeToLive(DescribeTimeToLiveRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeTimeToLiveRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeTimeToLiveResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeTimeToLiveEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Gives a description of the Time to Live (TTL) status on the specified table.
///
/// The name of the table to be described.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeTimeToLive service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DescribeTimeToLive Operation
public virtual Task DescribeTimeToLiveAsync(string tableName, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new DescribeTimeToLiveRequest();
request.TableName = tableName;
return DescribeTimeToLiveAsync(request, cancellationToken);
}
///
/// Gives a description of the Time to Live (TTL) status on the specified table.
///
/// Container for the necessary parameters to execute the DescribeTimeToLive service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DescribeTimeToLive service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DescribeTimeToLive Operation
public virtual Task DescribeTimeToLiveAsync(DescribeTimeToLiveRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DescribeTimeToLiveRequestMarshaller.Instance;
options.ResponseUnmarshaller = DescribeTimeToLiveResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DescribeTimeToLiveEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region DisableKinesisStreamingDestination
internal virtual DisableKinesisStreamingDestinationResponse DisableKinesisStreamingDestination(DisableKinesisStreamingDestinationRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = DisableKinesisStreamingDestinationRequestMarshaller.Instance;
options.ResponseUnmarshaller = DisableKinesisStreamingDestinationResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DisableKinesisStreamingDestinationEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Stops replication from the DynamoDB table to the Kinesis data stream. This is done
/// without deleting either of the resources.
///
/// Container for the necessary parameters to execute the DisableKinesisStreamingDestination service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the DisableKinesisStreamingDestination service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for DisableKinesisStreamingDestination Operation
public virtual Task DisableKinesisStreamingDestinationAsync(DisableKinesisStreamingDestinationRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = DisableKinesisStreamingDestinationRequestMarshaller.Instance;
options.ResponseUnmarshaller = DisableKinesisStreamingDestinationResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = DisableKinesisStreamingDestinationEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region EnableKinesisStreamingDestination
internal virtual EnableKinesisStreamingDestinationResponse EnableKinesisStreamingDestination(EnableKinesisStreamingDestinationRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = EnableKinesisStreamingDestinationRequestMarshaller.Instance;
options.ResponseUnmarshaller = EnableKinesisStreamingDestinationResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = EnableKinesisStreamingDestinationEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Starts table data replication to the specified Kinesis data stream at a timestamp
/// chosen during the enable workflow. If this operation doesn't return results immediately,
/// use DescribeKinesisStreamingDestination to check if streaming to the Kinesis data
/// stream is ACTIVE.
///
/// Container for the necessary parameters to execute the EnableKinesisStreamingDestination service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the EnableKinesisStreamingDestination service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for EnableKinesisStreamingDestination Operation
public virtual Task EnableKinesisStreamingDestinationAsync(EnableKinesisStreamingDestinationRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = EnableKinesisStreamingDestinationRequestMarshaller.Instance;
options.ResponseUnmarshaller = EnableKinesisStreamingDestinationResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = EnableKinesisStreamingDestinationEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ExecuteStatement
internal virtual ExecuteStatementResponse ExecuteStatement(ExecuteStatementRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ExecuteStatementRequestMarshaller.Instance;
options.ResponseUnmarshaller = ExecuteStatementResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// This operation allows you to perform reads and singleton writes on data stored in
/// DynamoDB, using PartiQL.
///
///
///
/// For PartiQL reads (SELECT statement), if the total number of processed
/// items exceeds the maximum dataset size limit of 1 MB, the read stops and results are
/// returned to the user as a LastEvaluatedKey value to continue the read
/// in a subsequent operation. If the filter criteria in WHERE clause does
/// not match any data, the read will return an empty result set.
///
///
///
/// A single SELECT statement response can return up to the maximum number
/// of items (if using the Limit parameter) or a maximum of 1 MB of data (and then apply
/// any filtering to the results using WHERE clause). If LastEvaluatedKey
/// is present in the response, you need to paginate the result set. If NextToken
/// is present, you need to paginate the result set and include NextToken.
///
///
/// Container for the necessary parameters to execute the ExecuteStatement service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ExecuteStatement service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// There was an attempt to insert an item with the same primary key as an item that
/// already exists in the DynamoDB table.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for ExecuteStatement Operation
public virtual Task ExecuteStatementAsync(ExecuteStatementRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ExecuteStatementRequestMarshaller.Instance;
options.ResponseUnmarshaller = ExecuteStatementResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ExecuteTransaction
internal virtual ExecuteTransactionResponse ExecuteTransaction(ExecuteTransactionRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ExecuteTransactionRequestMarshaller.Instance;
options.ResponseUnmarshaller = ExecuteTransactionResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// This operation allows you to perform transactional reads or writes on data stored
/// in DynamoDB, using PartiQL.
///
///
///
/// The entire transaction must consist of either read statements or write statements,
/// you cannot mix both in one transaction. The EXISTS function is an exception and can
/// be used to check the condition of specific attributes of the item in a similar manner
/// to ConditionCheck in the TransactWriteItems
/// API.
///
///
///
/// Container for the necessary parameters to execute the ExecuteTransaction service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ExecuteTransaction service method, as returned by DynamoDB.
///
/// DynamoDB rejected the request because you retried a request with a different payload
/// but with an idempotent token that was already used.
///
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// The entire transaction request was canceled.
///
///
///
/// DynamoDB cancels a TransactWriteItems request under the following circumstances:
///
/// -
///
/// A condition in one of the condition expressions is not met.
///
///
-
///
/// A table in the
TransactWriteItems request is in a different account or
/// region.
///
/// -
///
/// More than one action in the
TransactWriteItems operation targets the
/// same item.
///
/// -
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// An item size becomes too large (larger than 400 KB), or a local secondary index (LSI)
/// becomes too large, or a similar validation error occurs because of changes made by
/// the transaction.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
///
/// DynamoDB cancels a TransactGetItems request under the following circumstances:
///
/// -
///
/// There is an ongoing
TransactGetItems operation that conflicts with a
/// concurrent PutItem, UpdateItem, DeleteItem
/// or TransactWriteItems request. In this case the TransactGetItems
/// operation fails with a TransactionCanceledException.
///
/// -
///
/// A table in the
TransactGetItems request is in a different account or
/// region.
///
/// -
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
///
/// If using Java, DynamoDB lists the cancellation reasons on the CancellationReasons
/// property. This property is not set for other languages. Transaction cancellation reasons
/// are ordered in the order of requested items, if an item has no error it will have
/// None code and Null message.
///
///
///
/// Cancellation reason codes and possible error messages:
///
/// -
///
/// No Errors:
///
///
-
///
/// Code:
None
///
/// -
///
/// Message:
null
///
///
-
///
/// Conditional Check Failed:
///
///
-
///
/// Code:
ConditionalCheckFailed
///
/// -
///
/// Message: The conditional request failed.
///
///
-
///
/// Item Collection Size Limit Exceeded:
///
///
-
///
/// Code:
ItemCollectionSizeLimitExceeded
///
/// -
///
/// Message: Collection size exceeded.
///
///
-
///
/// Transaction Conflict:
///
///
-
///
/// Code:
TransactionConflict
///
/// -
///
/// Message: Transaction is ongoing for the item.
///
///
-
///
/// Provisioned Throughput Exceeded:
///
///
-
///
/// Code:
ProvisionedThroughputExceeded
///
/// -
///
/// Messages:
///
///
-
///
/// The level of configured provisioned throughput for the table was exceeded. Consider
/// increasing your provisioning level with the UpdateTable API.
///
///
///
/// This Message is received when provisioned throughput is exceeded is on a provisioned
/// DynamoDB table.
///
///
-
///
/// The level of configured provisioned throughput for one or more global secondary indexes
/// of the table was exceeded. Consider increasing your provisioning level for the under-provisioned
/// global secondary indexes with the UpdateTable API.
///
///
///
/// This message is returned when provisioned throughput is exceeded is on a provisioned
/// GSI.
///
///
-
///
/// Throttling Error:
///
///
-
///
/// Code:
ThrottlingError
///
/// -
///
/// Messages:
///
///
-
///
/// Throughput exceeds the current capacity of your table or index. DynamoDB is automatically
/// scaling your table or index so please try again shortly. If exceptions persist, check
/// if you have a hot key: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html.
///
///
///
/// This message is returned when writes get throttled on an On-Demand table as DynamoDB
/// is automatically scaling the table.
///
///
-
///
/// Throughput exceeds the current capacity for one or more global secondary indexes.
/// DynamoDB is automatically scaling your index so please try again shortly.
///
///
///
/// This message is returned when writes get throttled on an On-Demand GSI as DynamoDB
/// is automatically scaling the GSI.
///
///
-
///
/// Validation Error:
///
///
-
///
/// Code:
ValidationError
///
/// -
///
/// Messages:
///
///
-
///
/// One or more parameter values were invalid.
///
///
-
///
/// The update expression attempted to update the secondary index key beyond allowed size
/// limits.
///
///
-
///
/// The update expression attempted to update the secondary index key to unsupported type.
///
///
-
///
/// An operand in the update expression has an incorrect data type.
///
///
-
///
/// Item size to update has exceeded the maximum allowed size.
///
///
-
///
/// Number overflow. Attempting to store a number with magnitude larger than supported
/// range.
///
///
-
///
/// Type mismatch for attribute to update.
///
///
-
///
/// Nesting Levels have exceeded supported limits.
///
///
-
///
/// The document path provided in the update expression is invalid for update.
///
///
-
///
/// The provided expression refers to an attribute that does not exist in the item.
///
///
///
///
/// The transaction with the given request token is already in progress.
///
///
///
/// Recommended Settings
///
///
///
/// This is a general recommendation for handling the TransactionInProgressException.
/// These settings help ensure that the client retries will trigger completion of the
/// ongoing TransactWriteItems request.
///
/// -
///
/// Set
clientExecutionTimeout to a value that allows at least one retry
/// to be processed after 5 seconds have elapsed since the first attempt for the TransactWriteItems
/// operation.
///
/// -
///
/// Set
socketTimeout to a value a little lower than the requestTimeout
/// setting.
///
/// -
///
///
requestTimeout should be set based on the time taken for the individual
/// retries of a single HTTP request for your use case, but setting it to 1 second or
/// higher should work well to reduce chances of retries and TransactionInProgressException
/// errors.
///
/// -
///
/// Use exponential backoff when retrying and tune backoff if needed.
///
///
///
/// Assuming default
/// retry policy, example timeout settings based on the guidelines above are as follows:
///
///
///
///
/// Example timeline:
///
/// -
///
/// 0-1000 first attempt
///
///
-
///
/// 1000-1500 first sleep/delay (default retry policy uses 500 ms as base delay for 4xx
/// errors)
///
///
-
///
/// 1500-2500 second attempt
///
///
-
///
/// 2500-3500 second sleep/delay (500 * 2, exponential backoff)
///
///
-
///
/// 3500-4500 third attempt
///
///
-
///
/// 4500-6500 third sleep/delay (500 * 2^2)
///
///
-
///
/// 6500-7500 fourth attempt (this can trigger inline recovery since 5 seconds have elapsed
/// since the first attempt reached TC)
///
///
///
/// REST API Reference for ExecuteTransaction Operation
public virtual Task ExecuteTransactionAsync(ExecuteTransactionRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ExecuteTransactionRequestMarshaller.Instance;
options.ResponseUnmarshaller = ExecuteTransactionResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ExportTableToPointInTime
internal virtual ExportTableToPointInTimeResponse ExportTableToPointInTime(ExportTableToPointInTimeRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ExportTableToPointInTimeRequestMarshaller.Instance;
options.ResponseUnmarshaller = ExportTableToPointInTimeResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Exports table data to an S3 bucket. The table must have point in time recovery enabled,
/// and you can export data from any time within the point in time recovery window.
///
/// Container for the necessary parameters to execute the ExportTableToPointInTime service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ExportTableToPointInTime service method, as returned by DynamoDB.
///
/// There was a conflict when writing to the specified S3 bucket.
///
///
/// An error occurred on the server side.
///
///
/// The specified ExportTime is outside of the point in time recovery window.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// Point in time recovery has not yet been enabled for this source table.
///
///
/// A source table with the name TableName does not currently exist within
/// the subscriber's account or the subscriber is operating in the wrong Amazon Web Services
/// Region.
///
/// REST API Reference for ExportTableToPointInTime Operation
public virtual Task ExportTableToPointInTimeAsync(ExportTableToPointInTimeRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ExportTableToPointInTimeRequestMarshaller.Instance;
options.ResponseUnmarshaller = ExportTableToPointInTimeResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region GetItem
internal virtual GetItemResponse GetItem(GetItemRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = GetItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = GetItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = GetItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// The GetItem operation returns a set of attributes for the item with the
/// given primary key. If there is no matching item, GetItem does not return
/// any data and there will be no Item element in the response.
///
///
///
/// GetItem provides an eventually consistent read by default. If your application
/// requires a strongly consistent read, set ConsistentRead to true.
/// Although a strongly consistent read might take more time than an eventually consistent
/// read, it always returns the last updated value.
///
///
/// The name of the table containing the requested item.
/// A map of attribute names to AttributeValue objects, representing the primary key of the item to retrieve. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the GetItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for GetItem Operation
public virtual Task GetItemAsync(string tableName, Dictionary key, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new GetItemRequest();
request.TableName = tableName;
request.Key = key;
return GetItemAsync(request, cancellationToken);
}
///
/// The GetItem operation returns a set of attributes for the item with the
/// given primary key. If there is no matching item, GetItem does not return
/// any data and there will be no Item element in the response.
///
///
///
/// GetItem provides an eventually consistent read by default. If your application
/// requires a strongly consistent read, set ConsistentRead to true.
/// Although a strongly consistent read might take more time than an eventually consistent
/// read, it always returns the last updated value.
///
///
/// The name of the table containing the requested item.
/// A map of attribute names to AttributeValue objects, representing the primary key of the item to retrieve. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
/// Determines the read consistency model: If set to true, then the operation uses strongly consistent reads; otherwise, the operation uses eventually consistent reads.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the GetItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for GetItem Operation
public virtual Task GetItemAsync(string tableName, Dictionary key, bool consistentRead, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new GetItemRequest();
request.TableName = tableName;
request.Key = key;
request.ConsistentRead = consistentRead;
return GetItemAsync(request, cancellationToken);
}
///
/// The GetItem operation returns a set of attributes for the item with the
/// given primary key. If there is no matching item, GetItem does not return
/// any data and there will be no Item element in the response.
///
///
///
/// GetItem provides an eventually consistent read by default. If your application
/// requires a strongly consistent read, set ConsistentRead to true.
/// Although a strongly consistent read might take more time than an eventually consistent
/// read, it always returns the last updated value.
///
///
/// Container for the necessary parameters to execute the GetItem service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the GetItem service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for GetItem Operation
public virtual Task GetItemAsync(GetItemRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = GetItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = GetItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = GetItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ImportTable
internal virtual ImportTableResponse ImportTable(ImportTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ImportTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = ImportTableResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Imports table data from an S3 bucket.
///
/// Container for the necessary parameters to execute the ImportTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ImportTable service method, as returned by DynamoDB.
///
/// There was a conflict when importing from the specified S3 source. This can occur
/// when the current import conflicts with a previous import request that had the same
/// client token.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
/// REST API Reference for ImportTable Operation
public virtual Task ImportTableAsync(ImportTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ImportTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = ImportTableResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ListBackups
internal virtual ListBackupsResponse ListBackups(ListBackupsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ListBackupsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListBackupsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListBackupsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// List backups associated with an Amazon Web Services account. To list backups for a
/// given table, specify TableName. ListBackups returns a paginated
/// list of results with at most 1 MB worth of items in a page. You can also specify a
/// maximum number of entries to be returned in a page.
///
///
///
/// In the request, start time is inclusive, but end time is exclusive. Note that these
/// boundaries are for the time at which the original backup was requested.
///
///
///
/// You can call ListBackups a maximum of five times per second.
///
///
/// Container for the necessary parameters to execute the ListBackups service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListBackups service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for ListBackups Operation
public virtual Task ListBackupsAsync(ListBackupsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ListBackupsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListBackupsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListBackupsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ListContributorInsights
internal virtual ListContributorInsightsResponse ListContributorInsights(ListContributorInsightsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ListContributorInsightsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListContributorInsightsResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Returns a list of ContributorInsightsSummary for a table and all its global secondary
/// indexes.
///
/// Container for the necessary parameters to execute the ListContributorInsights service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListContributorInsights service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for ListContributorInsights Operation
public virtual Task ListContributorInsightsAsync(ListContributorInsightsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ListContributorInsightsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListContributorInsightsResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ListExports
internal virtual ListExportsResponse ListExports(ListExportsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ListExportsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListExportsResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Lists completed exports within the past 90 days.
///
/// Container for the necessary parameters to execute the ListExports service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListExports service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
/// REST API Reference for ListExports Operation
public virtual Task ListExportsAsync(ListExportsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ListExportsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListExportsResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ListGlobalTables
internal virtual ListGlobalTablesResponse ListGlobalTables(ListGlobalTablesRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ListGlobalTablesRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListGlobalTablesResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListGlobalTablesEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Lists all global tables that have a replica in the specified Region.
///
///
///
/// This operation only applies to Version
/// 2017.11.29 (Legacy) of global tables. We recommend using Version
/// 2019.11.21 (Current) when creating new global tables, as it provides greater flexibility,
/// higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine
/// which version you are using, see Determining
/// the version. To update existing global tables from version 2017.11.29 (Legacy)
/// to version 2019.11.21 (Current), see
/// Updating global tables.
///
///
///
/// Container for the necessary parameters to execute the ListGlobalTables service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListGlobalTables service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for ListGlobalTables Operation
public virtual Task ListGlobalTablesAsync(ListGlobalTablesRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ListGlobalTablesRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListGlobalTablesResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListGlobalTablesEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ListImports
internal virtual ListImportsResponse ListImports(ListImportsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ListImportsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListImportsResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Lists completed imports within the past 90 days.
///
/// Container for the necessary parameters to execute the ListImports service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListImports service method, as returned by DynamoDB.
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
/// REST API Reference for ListImports Operation
public virtual Task ListImportsAsync(ListImportsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ListImportsRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListImportsResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ListTables
internal virtual ListTablesResponse ListTables()
{
return ListTables(new ListTablesRequest());
}
internal virtual ListTablesResponse ListTables(ListTablesRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ListTablesRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListTablesResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListTablesEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Returns an array of table names associated with the current account and endpoint.
/// The output from ListTables is paginated, with each page returning a maximum
/// of 100 table names.
///
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListTables service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for ListTables Operation
public virtual Task ListTablesAsync(System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
return ListTablesAsync(new ListTablesRequest(), cancellationToken);
}
///
/// Returns an array of table names associated with the current account and endpoint.
/// The output from ListTables is paginated, with each page returning a maximum
/// of 100 table names.
///
/// The first table name that this operation will evaluate. Use the value that was returned for LastEvaluatedTableName in a previous operation, so that you can obtain the next page of results.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListTables service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for ListTables Operation
public virtual Task ListTablesAsync(string exclusiveStartTableName, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new ListTablesRequest();
request.ExclusiveStartTableName = exclusiveStartTableName;
return ListTablesAsync(request, cancellationToken);
}
///
/// Returns an array of table names associated with the current account and endpoint.
/// The output from ListTables is paginated, with each page returning a maximum
/// of 100 table names.
///
/// The first table name that this operation will evaluate. Use the value that was returned for LastEvaluatedTableName in a previous operation, so that you can obtain the next page of results.
/// A maximum number of table names to return. If this parameter is not specified, the limit is 100.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListTables service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for ListTables Operation
public virtual Task ListTablesAsync(string exclusiveStartTableName, int limit, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new ListTablesRequest();
request.ExclusiveStartTableName = exclusiveStartTableName;
request.Limit = limit;
return ListTablesAsync(request, cancellationToken);
}
///
/// Returns an array of table names associated with the current account and endpoint.
/// The output from ListTables is paginated, with each page returning a maximum
/// of 100 table names.
///
/// A maximum number of table names to return. If this parameter is not specified, the limit is 100.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListTables service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for ListTables Operation
public virtual Task ListTablesAsync(int limit, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new ListTablesRequest();
request.Limit = limit;
return ListTablesAsync(request, cancellationToken);
}
///
/// Returns an array of table names associated with the current account and endpoint.
/// The output from ListTables is paginated, with each page returning a maximum
/// of 100 table names.
///
/// Container for the necessary parameters to execute the ListTables service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListTables service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
/// REST API Reference for ListTables Operation
public virtual Task ListTablesAsync(ListTablesRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ListTablesRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListTablesResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListTablesEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region ListTagsOfResource
internal virtual ListTagsOfResourceResponse ListTagsOfResource(ListTagsOfResourceRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ListTagsOfResourceRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListTagsOfResourceResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListTagsOfResourceEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// List all tags on an Amazon DynamoDB resource. You can call ListTagsOfResource up to
/// 10 times per second, per account.
///
///
///
/// For an overview on tagging DynamoDB resources, see Tagging
/// for DynamoDB in the Amazon DynamoDB Developer Guide.
///
///
/// Container for the necessary parameters to execute the ListTagsOfResource service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the ListTagsOfResource service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for ListTagsOfResource Operation
public virtual Task ListTagsOfResourceAsync(ListTagsOfResourceRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ListTagsOfResourceRequestMarshaller.Instance;
options.ResponseUnmarshaller = ListTagsOfResourceResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ListTagsOfResourceEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region PutItem
internal virtual PutItemResponse PutItem(PutItemRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = PutItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = PutItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = PutItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Creates a new item, or replaces an old item with a new item. If an item that has the
/// same primary key as the new item already exists in the specified table, the new item
/// completely replaces the existing item. You can perform a conditional put operation
/// (add a new item if one with the specified primary key doesn't exist), or replace an
/// existing item if it has certain attribute values. You can return the item's attribute
/// values in the same operation, using the ReturnValues parameter.
///
///
///
/// When you add an item, the primary key attributes are the only required attributes.
///
///
///
///
/// Empty String and Binary attribute values are allowed. Attribute values of type String
/// and Binary must have a length greater than zero if the attribute is used as a key
/// attribute for a table or index. Set type attributes cannot be empty.
///
///
///
/// Invalid Requests with empty values will be rejected with a ValidationException
/// exception.
///
///
///
/// To prevent a new item from replacing an existing item, use a conditional expression
/// that contains the attribute_not_exists function with the name of the
/// attribute being used as the partition key for the table. Since every record must contain
/// that attribute, the attribute_not_exists function will only succeed if
/// no matching item exists.
///
///
///
/// For more information about PutItem, see Working
/// with Items in the Amazon DynamoDB Developer Guide.
///
///
/// The name of the table to contain the item.
/// A map of attribute name/value pairs, one for each attribute. Only the primary key attributes are required; you can optionally provide other attribute name-value pairs for the item. You must provide all of the attributes for the primary key. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide both values for both the partition key and the sort key. If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition. Empty String and Binary attribute values are allowed. Attribute values of type String and Binary must have a length greater than zero if the attribute is used as a key attribute for a table or index. For more information about primary keys, see Primary Key in the Amazon DynamoDB Developer Guide. Each element in the Item map is an AttributeValue object.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the PutItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for PutItem Operation
public virtual Task PutItemAsync(string tableName, Dictionary item, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new PutItemRequest();
request.TableName = tableName;
request.Item = item;
return PutItemAsync(request, cancellationToken);
}
///
/// Creates a new item, or replaces an old item with a new item. If an item that has the
/// same primary key as the new item already exists in the specified table, the new item
/// completely replaces the existing item. You can perform a conditional put operation
/// (add a new item if one with the specified primary key doesn't exist), or replace an
/// existing item if it has certain attribute values. You can return the item's attribute
/// values in the same operation, using the ReturnValues parameter.
///
///
///
/// When you add an item, the primary key attributes are the only required attributes.
///
///
///
///
/// Empty String and Binary attribute values are allowed. Attribute values of type String
/// and Binary must have a length greater than zero if the attribute is used as a key
/// attribute for a table or index. Set type attributes cannot be empty.
///
///
///
/// Invalid Requests with empty values will be rejected with a ValidationException
/// exception.
///
///
///
/// To prevent a new item from replacing an existing item, use a conditional expression
/// that contains the attribute_not_exists function with the name of the
/// attribute being used as the partition key for the table. Since every record must contain
/// that attribute, the attribute_not_exists function will only succeed if
/// no matching item exists.
///
///
///
/// For more information about PutItem, see Working
/// with Items in the Amazon DynamoDB Developer Guide.
///
///
/// The name of the table to contain the item.
/// A map of attribute name/value pairs, one for each attribute. Only the primary key attributes are required; you can optionally provide other attribute name-value pairs for the item. You must provide all of the attributes for the primary key. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide both values for both the partition key and the sort key. If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition. Empty String and Binary attribute values are allowed. Attribute values of type String and Binary must have a length greater than zero if the attribute is used as a key attribute for a table or index. For more information about primary keys, see Primary Key in the Amazon DynamoDB Developer Guide. Each element in the Item map is an AttributeValue object.
/// Use ReturnValues if you want to get the item attributes as they appeared before they were updated with the PutItem request. For PutItem, the valid values are: -
NONE - If ReturnValues is not specified, or if its value is NONE, then nothing is returned. (This setting is the default for ReturnValues.) -
ALL_OLD - If PutItem overwrote an attribute name-value pair, then the content of the old item is returned.
The values returned are strongly consistent. There is no additional cost associated with requesting a return value aside from the small network and processing overhead of receiving a larger response. No read capacity units are consumed. The ReturnValues parameter is used by several DynamoDB operations; however, PutItem does not recognize any values other than NONE or ALL_OLD.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the PutItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for PutItem Operation
public virtual Task PutItemAsync(string tableName, Dictionary item, ReturnValue returnValues, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new PutItemRequest();
request.TableName = tableName;
request.Item = item;
request.ReturnValues = returnValues;
return PutItemAsync(request, cancellationToken);
}
///
/// Creates a new item, or replaces an old item with a new item. If an item that has the
/// same primary key as the new item already exists in the specified table, the new item
/// completely replaces the existing item. You can perform a conditional put operation
/// (add a new item if one with the specified primary key doesn't exist), or replace an
/// existing item if it has certain attribute values. You can return the item's attribute
/// values in the same operation, using the ReturnValues parameter.
///
///
///
/// When you add an item, the primary key attributes are the only required attributes.
///
///
///
///
/// Empty String and Binary attribute values are allowed. Attribute values of type String
/// and Binary must have a length greater than zero if the attribute is used as a key
/// attribute for a table or index. Set type attributes cannot be empty.
///
///
///
/// Invalid Requests with empty values will be rejected with a ValidationException
/// exception.
///
///
///
/// To prevent a new item from replacing an existing item, use a conditional expression
/// that contains the attribute_not_exists function with the name of the
/// attribute being used as the partition key for the table. Since every record must contain
/// that attribute, the attribute_not_exists function will only succeed if
/// no matching item exists.
///
///
///
/// For more information about PutItem, see Working
/// with Items in the Amazon DynamoDB Developer Guide.
///
///
/// Container for the necessary parameters to execute the PutItem service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the PutItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for PutItem Operation
public virtual Task PutItemAsync(PutItemRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = PutItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = PutItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = PutItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region Query
internal virtual QueryResponse Query(QueryRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = QueryRequestMarshaller.Instance;
options.ResponseUnmarshaller = QueryResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = QueryEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// You must provide the name of the partition key attribute and a single value for that
/// attribute. Query returns all items with that partition key value. Optionally,
/// you can provide a sort key attribute and use a comparison operator to refine the search
/// results.
///
///
///
/// Use the KeyConditionExpression parameter to provide a specific value
/// for the partition key. The Query operation will return all of the items
/// from the table or index with that partition key value. You can optionally narrow the
/// scope of the Query operation by specifying a sort key value and a comparison
/// operator in KeyConditionExpression. To further refine the Query
/// results, you can optionally provide a FilterExpression. A FilterExpression
/// determines which items within the results should be returned to you. All of the other
/// results are discarded.
///
///
///
/// A Query operation always returns a result set. If no matching items
/// are found, the result set will be empty. Queries that do not return results consume
/// the minimum number of read capacity units for that type of read operation.
///
///
///
/// DynamoDB calculates the number of read capacity units consumed based on item size,
/// not on the amount of data that is returned to an application. The number of capacity
/// units consumed will be the same whether you request all of the attributes (the default
/// behavior) or just some of them (using a projection expression). The number will also
/// be the same whether or not you use a FilterExpression.
///
///
///
/// Query results are always sorted by the sort key value. If the data type
/// of the sort key is Number, the results are returned in numeric order; otherwise, the
/// results are returned in order of UTF-8 bytes. By default, the sort order is ascending.
/// To reverse the order, set the ScanIndexForward parameter to false.
///
///
///
/// A single Query operation will read up to the maximum number of items
/// set (if using the Limit parameter) or a maximum of 1 MB of data and then
/// apply any filtering to the results using FilterExpression. If LastEvaluatedKey
/// is present in the response, you will need to paginate the result set. For more information,
/// see Paginating
/// the Results in the Amazon DynamoDB Developer Guide.
///
///
///
/// FilterExpression is applied after a Query finishes, but
/// before the results are returned. A FilterExpression cannot contain partition
/// key or sort key attributes. You need to specify those attributes in the KeyConditionExpression.
///
///
///
///
/// A Query operation can return an empty result set and a LastEvaluatedKey
/// if all the items read for the page of results are filtered out.
///
///
///
/// You can query a table, a local secondary index, or a global secondary index. For a
/// query on a table or on a local secondary index, you can set the ConsistentRead
/// parameter to true and obtain a strongly consistent result. Global secondary
/// indexes support eventually consistent reads only, so do not specify ConsistentRead
/// when querying a global secondary index.
///
///
/// Container for the necessary parameters to execute the Query service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the Query service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for Query Operation
public virtual Task QueryAsync(QueryRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = QueryRequestMarshaller.Instance;
options.ResponseUnmarshaller = QueryResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = QueryEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region RestoreTableFromBackup
internal virtual RestoreTableFromBackupResponse RestoreTableFromBackup(RestoreTableFromBackupRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = RestoreTableFromBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = RestoreTableFromBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = RestoreTableFromBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Creates a new table from an existing backup. Any number of users can execute up to
/// 50 concurrent restores (any type of restore) in a given account.
///
///
///
/// You can call RestoreTableFromBackup at a maximum rate of 10 times per
/// second.
///
///
///
/// You must manually set up the following on the restored table:
///
/// -
///
/// Auto scaling policies
///
///
-
///
/// IAM policies
///
///
-
///
/// Amazon CloudWatch metrics and alarms
///
///
-
///
/// Tags
///
///
-
///
/// Stream settings
///
///
-
///
/// Time to Live (TTL) settings
///
///
///
/// Container for the necessary parameters to execute the RestoreTableFromBackup service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the RestoreTableFromBackup service method, as returned by DynamoDB.
///
/// There is another ongoing conflicting backup control plane operation on the table.
/// The backup is either being created, deleted or restored to a table.
///
///
/// Backup not found for the given BackupARN.
///
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// A target table with the specified name already exists.
///
///
/// A target table with the specified name is either being created or deleted.
///
/// REST API Reference for RestoreTableFromBackup Operation
public virtual Task RestoreTableFromBackupAsync(RestoreTableFromBackupRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = RestoreTableFromBackupRequestMarshaller.Instance;
options.ResponseUnmarshaller = RestoreTableFromBackupResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = RestoreTableFromBackupEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region RestoreTableToPointInTime
internal virtual RestoreTableToPointInTimeResponse RestoreTableToPointInTime(RestoreTableToPointInTimeRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = RestoreTableToPointInTimeRequestMarshaller.Instance;
options.ResponseUnmarshaller = RestoreTableToPointInTimeResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = RestoreTableToPointInTimeEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Restores the specified table to the specified point in time within EarliestRestorableDateTime
/// and LatestRestorableDateTime. You can restore your table to any point
/// in time during the last 35 days. Any number of users can execute up to 4 concurrent
/// restores (any type of restore) in a given account.
///
///
///
/// When you restore using point in time recovery, DynamoDB restores your table data
/// to the state based on the selected date and time (day:hour:minute:second) to a new
/// table.
///
///
///
/// Along with data, the following are also included on the new restored table using
/// point in time recovery:
///
/// -
///
/// Global secondary indexes (GSIs)
///
///
-
///
/// Local secondary indexes (LSIs)
///
///
-
///
/// Provisioned read and write capacity
///
///
-
///
/// Encryption settings
///
///
///
/// All these settings come from the current settings of the source table at the time
/// of restore.
///
///
///
/// You must manually set up the following on the restored table:
///
/// -
///
/// Auto scaling policies
///
///
-
///
/// IAM policies
///
///
-
///
/// Amazon CloudWatch metrics and alarms
///
///
-
///
/// Tags
///
///
-
///
/// Stream settings
///
///
-
///
/// Time to Live (TTL) settings
///
///
-
///
/// Point in time recovery settings
///
///
///
/// Container for the necessary parameters to execute the RestoreTableToPointInTime service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the RestoreTableToPointInTime service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// An invalid restore time was specified. RestoreDateTime must be between EarliestRestorableDateTime
/// and LatestRestorableDateTime.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// Point in time recovery has not yet been enabled for this source table.
///
///
/// A target table with the specified name already exists.
///
///
/// A target table with the specified name is either being created or deleted.
///
///
/// A source table with the name TableName does not currently exist within
/// the subscriber's account or the subscriber is operating in the wrong Amazon Web Services
/// Region.
///
/// REST API Reference for RestoreTableToPointInTime Operation
public virtual Task RestoreTableToPointInTimeAsync(RestoreTableToPointInTimeRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = RestoreTableToPointInTimeRequestMarshaller.Instance;
options.ResponseUnmarshaller = RestoreTableToPointInTimeResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = RestoreTableToPointInTimeEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region Scan
internal virtual ScanResponse Scan(ScanRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = ScanRequestMarshaller.Instance;
options.ResponseUnmarshaller = ScanResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ScanEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// The Scan operation returns one or more items and item attributes by accessing
/// every item in a table or a secondary index. To have DynamoDB return fewer items, you
/// can provide a FilterExpression operation.
///
///
///
/// If the total size of scanned items exceeds the maximum dataset size limit of 1 MB,
/// the scan completes and results are returned to the user. The LastEvaluatedKey
/// value is also returned and the requestor can use the LastEvaluatedKey
/// to continue the scan in a subsequent operation. Each scan response also includes number
/// of items that were scanned (ScannedCount) as part of the request. If using a FilterExpression,
/// a scan result can result in no items meeting the criteria and the Count
/// will result in zero. If you did not use a FilterExpression in the scan
/// request, then Count is the same as ScannedCount.
///
///
///
/// Count and ScannedCount only return the count of items specific
/// to a single scan request and, unless the table is less than 1MB, do not represent
/// the total number of items in the table.
///
///
///
/// A single Scan operation first reads up to the maximum number of items
/// set (if using the Limit parameter) or a maximum of 1 MB of data and then
/// applies any filtering to the results if a FilterExpression is provided.
/// If LastEvaluatedKey is present in the response, pagination is required
/// to complete the full table scan. For more information, see Paginating
/// the Results in the Amazon DynamoDB Developer Guide.
///
///
///
/// Scan operations proceed sequentially; however, for faster performance
/// on a large table or secondary index, applications can request a parallel Scan
/// operation by providing the Segment and TotalSegments parameters.
/// For more information, see Parallel
/// Scan in the Amazon DynamoDB Developer Guide.
///
///
///
/// By default, a Scan uses eventually consistent reads when accessing the
/// items in a table. Therefore, the results from an eventually consistent Scan
/// may not include the latest item changes at the time the scan iterates through each
/// item in the table. If you require a strongly consistent read of each item as the scan
/// iterates through the items in the table, you can set the ConsistentRead
/// parameter to true. Strong consistency only relates to the consistency of the read
/// at the item level.
///
///
///
/// DynamoDB does not provide snapshot isolation for a scan operation when the ConsistentRead
/// parameter is set to true. Thus, a DynamoDB scan operation does not guarantee that
/// all reads in a scan see a consistent snapshot of the table when the scan operation
/// was requested.
///
///
///
/// The name of the table containing the requested items; or, if you provide IndexName, the name of the table to which that index belongs.
/// This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the Scan service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for Scan Operation
public virtual Task ScanAsync(string tableName, List attributesToGet, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new ScanRequest();
request.TableName = tableName;
request.AttributesToGet = attributesToGet;
return ScanAsync(request, cancellationToken);
}
///
/// The Scan operation returns one or more items and item attributes by accessing
/// every item in a table or a secondary index. To have DynamoDB return fewer items, you
/// can provide a FilterExpression operation.
///
///
///
/// If the total size of scanned items exceeds the maximum dataset size limit of 1 MB,
/// the scan completes and results are returned to the user. The LastEvaluatedKey
/// value is also returned and the requestor can use the LastEvaluatedKey
/// to continue the scan in a subsequent operation. Each scan response also includes number
/// of items that were scanned (ScannedCount) as part of the request. If using a FilterExpression,
/// a scan result can result in no items meeting the criteria and the Count
/// will result in zero. If you did not use a FilterExpression in the scan
/// request, then Count is the same as ScannedCount.
///
///
///
/// Count and ScannedCount only return the count of items specific
/// to a single scan request and, unless the table is less than 1MB, do not represent
/// the total number of items in the table.
///
///
///
/// A single Scan operation first reads up to the maximum number of items
/// set (if using the Limit parameter) or a maximum of 1 MB of data and then
/// applies any filtering to the results if a FilterExpression is provided.
/// If LastEvaluatedKey is present in the response, pagination is required
/// to complete the full table scan. For more information, see Paginating
/// the Results in the Amazon DynamoDB Developer Guide.
///
///
///
/// Scan operations proceed sequentially; however, for faster performance
/// on a large table or secondary index, applications can request a parallel Scan
/// operation by providing the Segment and TotalSegments parameters.
/// For more information, see Parallel
/// Scan in the Amazon DynamoDB Developer Guide.
///
///
///
/// By default, a Scan uses eventually consistent reads when accessing the
/// items in a table. Therefore, the results from an eventually consistent Scan
/// may not include the latest item changes at the time the scan iterates through each
/// item in the table. If you require a strongly consistent read of each item as the scan
/// iterates through the items in the table, you can set the ConsistentRead
/// parameter to true. Strong consistency only relates to the consistency of the read
/// at the item level.
///
///
///
/// DynamoDB does not provide snapshot isolation for a scan operation when the ConsistentRead
/// parameter is set to true. Thus, a DynamoDB scan operation does not guarantee that
/// all reads in a scan see a consistent snapshot of the table when the scan operation
/// was requested.
///
///
///
/// The name of the table containing the requested items; or, if you provide IndexName, the name of the table to which that index belongs.
/// This is a legacy parameter. Use FilterExpression instead. For more information, see ScanFilter in the Amazon DynamoDB Developer Guide.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the Scan service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for Scan Operation
public virtual Task ScanAsync(string tableName, Dictionary scanFilter, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new ScanRequest();
request.TableName = tableName;
request.ScanFilter = scanFilter;
return ScanAsync(request, cancellationToken);
}
///
/// The Scan operation returns one or more items and item attributes by accessing
/// every item in a table or a secondary index. To have DynamoDB return fewer items, you
/// can provide a FilterExpression operation.
///
///
///
/// If the total size of scanned items exceeds the maximum dataset size limit of 1 MB,
/// the scan completes and results are returned to the user. The LastEvaluatedKey
/// value is also returned and the requestor can use the LastEvaluatedKey
/// to continue the scan in a subsequent operation. Each scan response also includes number
/// of items that were scanned (ScannedCount) as part of the request. If using a FilterExpression,
/// a scan result can result in no items meeting the criteria and the Count
/// will result in zero. If you did not use a FilterExpression in the scan
/// request, then Count is the same as ScannedCount.
///
///
///
/// Count and ScannedCount only return the count of items specific
/// to a single scan request and, unless the table is less than 1MB, do not represent
/// the total number of items in the table.
///
///
///
/// A single Scan operation first reads up to the maximum number of items
/// set (if using the Limit parameter) or a maximum of 1 MB of data and then
/// applies any filtering to the results if a FilterExpression is provided.
/// If LastEvaluatedKey is present in the response, pagination is required
/// to complete the full table scan. For more information, see Paginating
/// the Results in the Amazon DynamoDB Developer Guide.
///
///
///
/// Scan operations proceed sequentially; however, for faster performance
/// on a large table or secondary index, applications can request a parallel Scan
/// operation by providing the Segment and TotalSegments parameters.
/// For more information, see Parallel
/// Scan in the Amazon DynamoDB Developer Guide.
///
///
///
/// By default, a Scan uses eventually consistent reads when accessing the
/// items in a table. Therefore, the results from an eventually consistent Scan
/// may not include the latest item changes at the time the scan iterates through each
/// item in the table. If you require a strongly consistent read of each item as the scan
/// iterates through the items in the table, you can set the ConsistentRead
/// parameter to true. Strong consistency only relates to the consistency of the read
/// at the item level.
///
///
///
/// DynamoDB does not provide snapshot isolation for a scan operation when the ConsistentRead
/// parameter is set to true. Thus, a DynamoDB scan operation does not guarantee that
/// all reads in a scan see a consistent snapshot of the table when the scan operation
/// was requested.
///
///
///
/// The name of the table containing the requested items; or, if you provide IndexName, the name of the table to which that index belongs.
/// This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
/// This is a legacy parameter. Use FilterExpression instead. For more information, see ScanFilter in the Amazon DynamoDB Developer Guide.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the Scan service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for Scan Operation
public virtual Task ScanAsync(string tableName, List attributesToGet, Dictionary scanFilter, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new ScanRequest();
request.TableName = tableName;
request.AttributesToGet = attributesToGet;
request.ScanFilter = scanFilter;
return ScanAsync(request, cancellationToken);
}
///
/// The Scan operation returns one or more items and item attributes by accessing
/// every item in a table or a secondary index. To have DynamoDB return fewer items, you
/// can provide a FilterExpression operation.
///
///
///
/// If the total size of scanned items exceeds the maximum dataset size limit of 1 MB,
/// the scan completes and results are returned to the user. The LastEvaluatedKey
/// value is also returned and the requestor can use the LastEvaluatedKey
/// to continue the scan in a subsequent operation. Each scan response also includes number
/// of items that were scanned (ScannedCount) as part of the request. If using a FilterExpression,
/// a scan result can result in no items meeting the criteria and the Count
/// will result in zero. If you did not use a FilterExpression in the scan
/// request, then Count is the same as ScannedCount.
///
///
///
/// Count and ScannedCount only return the count of items specific
/// to a single scan request and, unless the table is less than 1MB, do not represent
/// the total number of items in the table.
///
///
///
/// A single Scan operation first reads up to the maximum number of items
/// set (if using the Limit parameter) or a maximum of 1 MB of data and then
/// applies any filtering to the results if a FilterExpression is provided.
/// If LastEvaluatedKey is present in the response, pagination is required
/// to complete the full table scan. For more information, see Paginating
/// the Results in the Amazon DynamoDB Developer Guide.
///
///
///
/// Scan operations proceed sequentially; however, for faster performance
/// on a large table or secondary index, applications can request a parallel Scan
/// operation by providing the Segment and TotalSegments parameters.
/// For more information, see Parallel
/// Scan in the Amazon DynamoDB Developer Guide.
///
///
///
/// By default, a Scan uses eventually consistent reads when accessing the
/// items in a table. Therefore, the results from an eventually consistent Scan
/// may not include the latest item changes at the time the scan iterates through each
/// item in the table. If you require a strongly consistent read of each item as the scan
/// iterates through the items in the table, you can set the ConsistentRead
/// parameter to true. Strong consistency only relates to the consistency of the read
/// at the item level.
///
///
///
/// DynamoDB does not provide snapshot isolation for a scan operation when the ConsistentRead
/// parameter is set to true. Thus, a DynamoDB scan operation does not guarantee that
/// all reads in a scan see a consistent snapshot of the table when the scan operation
/// was requested.
///
///
///
/// Container for the necessary parameters to execute the Scan service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the Scan service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for Scan Operation
public virtual Task ScanAsync(ScanRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = ScanRequestMarshaller.Instance;
options.ResponseUnmarshaller = ScanResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = ScanEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region TagResource
internal virtual TagResourceResponse TagResource(TagResourceRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = TagResourceRequestMarshaller.Instance;
options.ResponseUnmarshaller = TagResourceResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = TagResourceEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Associate a set of tags with an Amazon DynamoDB resource. You can then activate these
/// user-defined tags so that they appear on the Billing and Cost Management console for
/// cost allocation tracking. You can call TagResource up to five times per second, per
/// account.
///
///
///
/// For an overview on tagging DynamoDB resources, see Tagging
/// for DynamoDB in the Amazon DynamoDB Developer Guide.
///
///
/// Container for the necessary parameters to execute the TagResource service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the TagResource service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for TagResource Operation
public virtual Task TagResourceAsync(TagResourceRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = TagResourceRequestMarshaller.Instance;
options.ResponseUnmarshaller = TagResourceResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = TagResourceEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region TransactGetItems
internal virtual TransactGetItemsResponse TransactGetItems(TransactGetItemsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = TransactGetItemsRequestMarshaller.Instance;
options.ResponseUnmarshaller = TransactGetItemsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = TransactGetItemsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// TransactGetItems is a synchronous operation that atomically retrieves
/// multiple items from one or more tables (but not from indexes) in a single account
/// and Region. A TransactGetItems call can contain up to 100 TransactGetItem
/// objects, each of which contains a Get structure that specifies an item
/// to retrieve from a table in the account and Region. A call to TransactGetItems
/// cannot retrieve items from tables in more than one Amazon Web Services account or
/// Region. The aggregate size of the items in the transaction cannot exceed 4 MB.
///
///
///
/// DynamoDB rejects the entire TransactGetItems request if any of the following
/// is true:
///
/// -
///
/// A conflicting operation is in the process of updating an item to be read.
///
///
-
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
-
///
/// The aggregate size of the items in the transaction exceeded 4 MB.
///
///
///
/// Container for the necessary parameters to execute the TransactGetItems service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the TransactGetItems service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// The entire transaction request was canceled.
///
///
///
/// DynamoDB cancels a TransactWriteItems request under the following circumstances:
///
/// -
///
/// A condition in one of the condition expressions is not met.
///
///
-
///
/// A table in the
TransactWriteItems request is in a different account or
/// region.
///
/// -
///
/// More than one action in the
TransactWriteItems operation targets the
/// same item.
///
/// -
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// An item size becomes too large (larger than 400 KB), or a local secondary index (LSI)
/// becomes too large, or a similar validation error occurs because of changes made by
/// the transaction.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
///
/// DynamoDB cancels a TransactGetItems request under the following circumstances:
///
/// -
///
/// There is an ongoing
TransactGetItems operation that conflicts with a
/// concurrent PutItem, UpdateItem, DeleteItem
/// or TransactWriteItems request. In this case the TransactGetItems
/// operation fails with a TransactionCanceledException.
///
/// -
///
/// A table in the
TransactGetItems request is in a different account or
/// region.
///
/// -
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
///
/// If using Java, DynamoDB lists the cancellation reasons on the CancellationReasons
/// property. This property is not set for other languages. Transaction cancellation reasons
/// are ordered in the order of requested items, if an item has no error it will have
/// None code and Null message.
///
///
///
/// Cancellation reason codes and possible error messages:
///
/// -
///
/// No Errors:
///
///
-
///
/// Code:
None
///
/// -
///
/// Message:
null
///
///
-
///
/// Conditional Check Failed:
///
///
-
///
/// Code:
ConditionalCheckFailed
///
/// -
///
/// Message: The conditional request failed.
///
///
-
///
/// Item Collection Size Limit Exceeded:
///
///
-
///
/// Code:
ItemCollectionSizeLimitExceeded
///
/// -
///
/// Message: Collection size exceeded.
///
///
-
///
/// Transaction Conflict:
///
///
-
///
/// Code:
TransactionConflict
///
/// -
///
/// Message: Transaction is ongoing for the item.
///
///
-
///
/// Provisioned Throughput Exceeded:
///
///
-
///
/// Code:
ProvisionedThroughputExceeded
///
/// -
///
/// Messages:
///
///
-
///
/// The level of configured provisioned throughput for the table was exceeded. Consider
/// increasing your provisioning level with the UpdateTable API.
///
///
///
/// This Message is received when provisioned throughput is exceeded is on a provisioned
/// DynamoDB table.
///
///
-
///
/// The level of configured provisioned throughput for one or more global secondary indexes
/// of the table was exceeded. Consider increasing your provisioning level for the under-provisioned
/// global secondary indexes with the UpdateTable API.
///
///
///
/// This message is returned when provisioned throughput is exceeded is on a provisioned
/// GSI.
///
///
-
///
/// Throttling Error:
///
///
-
///
/// Code:
ThrottlingError
///
/// -
///
/// Messages:
///
///
-
///
/// Throughput exceeds the current capacity of your table or index. DynamoDB is automatically
/// scaling your table or index so please try again shortly. If exceptions persist, check
/// if you have a hot key: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html.
///
///
///
/// This message is returned when writes get throttled on an On-Demand table as DynamoDB
/// is automatically scaling the table.
///
///
-
///
/// Throughput exceeds the current capacity for one or more global secondary indexes.
/// DynamoDB is automatically scaling your index so please try again shortly.
///
///
///
/// This message is returned when writes get throttled on an On-Demand GSI as DynamoDB
/// is automatically scaling the GSI.
///
///
-
///
/// Validation Error:
///
///
-
///
/// Code:
ValidationError
///
/// -
///
/// Messages:
///
///
-
///
/// One or more parameter values were invalid.
///
///
-
///
/// The update expression attempted to update the secondary index key beyond allowed size
/// limits.
///
///
-
///
/// The update expression attempted to update the secondary index key to unsupported type.
///
///
-
///
/// An operand in the update expression has an incorrect data type.
///
///
-
///
/// Item size to update has exceeded the maximum allowed size.
///
///
-
///
/// Number overflow. Attempting to store a number with magnitude larger than supported
/// range.
///
///
-
///
/// Type mismatch for attribute to update.
///
///
-
///
/// Nesting Levels have exceeded supported limits.
///
///
-
///
/// The document path provided in the update expression is invalid for update.
///
///
-
///
/// The provided expression refers to an attribute that does not exist in the item.
///
///
///
/// REST API Reference for TransactGetItems Operation
public virtual Task TransactGetItemsAsync(TransactGetItemsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = TransactGetItemsRequestMarshaller.Instance;
options.ResponseUnmarshaller = TransactGetItemsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = TransactGetItemsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region TransactWriteItems
internal virtual TransactWriteItemsResponse TransactWriteItems(TransactWriteItemsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = TransactWriteItemsRequestMarshaller.Instance;
options.ResponseUnmarshaller = TransactWriteItemsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = TransactWriteItemsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// TransactWriteItems is a synchronous write operation that groups up to
/// 100 action requests. These actions can target items in different tables, but not in
/// different Amazon Web Services accounts or Regions, and no two actions can target the
/// same item. For example, you cannot both ConditionCheck and Update
/// the same item. The aggregate size of the items in the transaction cannot exceed 4
/// MB.
///
///
///
/// The actions are completed atomically so that either all of them succeed, or all of
/// them fail. They are defined by the following objects:
///
/// -
///
///
Put — Initiates a PutItem operation to write a new item.
/// This structure specifies the primary key of the item to be written, the name of the
/// table to write it in, an optional condition expression that must be satisfied for
/// the write to succeed, a list of the item's attributes, and a field indicating whether
/// to retrieve the item's attributes if the condition is not met.
///
/// -
///
///
Update — Initiates an UpdateItem operation to update
/// an existing item. This structure specifies the primary key of the item to be updated,
/// the name of the table where it resides, an optional condition expression that must
/// be satisfied for the update to succeed, an expression that defines one or more attributes
/// to be updated, and a field indicating whether to retrieve the item's attributes if
/// the condition is not met.
///
/// -
///
///
Delete — Initiates a DeleteItem operation to delete
/// an existing item. This structure specifies the primary key of the item to be deleted,
/// the name of the table where it resides, an optional condition expression that must
/// be satisfied for the deletion to succeed, and a field indicating whether to retrieve
/// the item's attributes if the condition is not met.
///
/// -
///
///
ConditionCheck — Applies a condition to an item that is not being
/// modified by the transaction. This structure specifies the primary key of the item
/// to be checked, the name of the table where it resides, a condition expression that
/// must be satisfied for the transaction to succeed, and a field indicating whether to
/// retrieve the item's attributes if the condition is not met.
///
///
///
/// DynamoDB rejects the entire TransactWriteItems request if any of the
/// following is true:
///
/// -
///
/// A condition in one of the condition expressions is not met.
///
///
-
///
/// An ongoing operation is in the process of updating the same item.
///
///
-
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// An item size becomes too large (bigger than 400 KB), a local secondary index (LSI)
/// becomes too large, or a similar validation error occurs because of changes made by
/// the transaction.
///
///
-
///
/// The aggregate size of the items in the transaction exceeds 4 MB.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
///
/// Container for the necessary parameters to execute the TransactWriteItems service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the TransactWriteItems service method, as returned by DynamoDB.
///
/// DynamoDB rejected the request because you retried a request with a different payload
/// but with an idempotent token that was already used.
///
///
/// An error occurred on the server side.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// The entire transaction request was canceled.
///
///
///
/// DynamoDB cancels a TransactWriteItems request under the following circumstances:
///
/// -
///
/// A condition in one of the condition expressions is not met.
///
///
-
///
/// A table in the
TransactWriteItems request is in a different account or
/// region.
///
/// -
///
/// More than one action in the
TransactWriteItems operation targets the
/// same item.
///
/// -
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// An item size becomes too large (larger than 400 KB), or a local secondary index (LSI)
/// becomes too large, or a similar validation error occurs because of changes made by
/// the transaction.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
///
/// DynamoDB cancels a TransactGetItems request under the following circumstances:
///
/// -
///
/// There is an ongoing
TransactGetItems operation that conflicts with a
/// concurrent PutItem, UpdateItem, DeleteItem
/// or TransactWriteItems request. In this case the TransactGetItems
/// operation fails with a TransactionCanceledException.
///
/// -
///
/// A table in the
TransactGetItems request is in a different account or
/// region.
///
/// -
///
/// There is insufficient provisioned capacity for the transaction to be completed.
///
///
-
///
/// There is a user error, such as an invalid data format.
///
///
///
/// If using Java, DynamoDB lists the cancellation reasons on the CancellationReasons
/// property. This property is not set for other languages. Transaction cancellation reasons
/// are ordered in the order of requested items, if an item has no error it will have
/// None code and Null message.
///
///
///
/// Cancellation reason codes and possible error messages:
///
/// -
///
/// No Errors:
///
///
-
///
/// Code:
None
///
/// -
///
/// Message:
null
///
///
-
///
/// Conditional Check Failed:
///
///
-
///
/// Code:
ConditionalCheckFailed
///
/// -
///
/// Message: The conditional request failed.
///
///
-
///
/// Item Collection Size Limit Exceeded:
///
///
-
///
/// Code:
ItemCollectionSizeLimitExceeded
///
/// -
///
/// Message: Collection size exceeded.
///
///
-
///
/// Transaction Conflict:
///
///
-
///
/// Code:
TransactionConflict
///
/// -
///
/// Message: Transaction is ongoing for the item.
///
///
-
///
/// Provisioned Throughput Exceeded:
///
///
-
///
/// Code:
ProvisionedThroughputExceeded
///
/// -
///
/// Messages:
///
///
-
///
/// The level of configured provisioned throughput for the table was exceeded. Consider
/// increasing your provisioning level with the UpdateTable API.
///
///
///
/// This Message is received when provisioned throughput is exceeded is on a provisioned
/// DynamoDB table.
///
///
-
///
/// The level of configured provisioned throughput for one or more global secondary indexes
/// of the table was exceeded. Consider increasing your provisioning level for the under-provisioned
/// global secondary indexes with the UpdateTable API.
///
///
///
/// This message is returned when provisioned throughput is exceeded is on a provisioned
/// GSI.
///
///
-
///
/// Throttling Error:
///
///
-
///
/// Code:
ThrottlingError
///
/// -
///
/// Messages:
///
///
-
///
/// Throughput exceeds the current capacity of your table or index. DynamoDB is automatically
/// scaling your table or index so please try again shortly. If exceptions persist, check
/// if you have a hot key: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html.
///
///
///
/// This message is returned when writes get throttled on an On-Demand table as DynamoDB
/// is automatically scaling the table.
///
///
-
///
/// Throughput exceeds the current capacity for one or more global secondary indexes.
/// DynamoDB is automatically scaling your index so please try again shortly.
///
///
///
/// This message is returned when writes get throttled on an On-Demand GSI as DynamoDB
/// is automatically scaling the GSI.
///
///
-
///
/// Validation Error:
///
///
-
///
/// Code:
ValidationError
///
/// -
///
/// Messages:
///
///
-
///
/// One or more parameter values were invalid.
///
///
-
///
/// The update expression attempted to update the secondary index key beyond allowed size
/// limits.
///
///
-
///
/// The update expression attempted to update the secondary index key to unsupported type.
///
///
-
///
/// An operand in the update expression has an incorrect data type.
///
///
-
///
/// Item size to update has exceeded the maximum allowed size.
///
///
-
///
/// Number overflow. Attempting to store a number with magnitude larger than supported
/// range.
///
///
-
///
/// Type mismatch for attribute to update.
///
///
-
///
/// Nesting Levels have exceeded supported limits.
///
///
-
///
/// The document path provided in the update expression is invalid for update.
///
///
-
///
/// The provided expression refers to an attribute that does not exist in the item.
///
///
///
///
/// The transaction with the given request token is already in progress.
///
///
///
/// Recommended Settings
///
///
///
/// This is a general recommendation for handling the TransactionInProgressException.
/// These settings help ensure that the client retries will trigger completion of the
/// ongoing TransactWriteItems request.
///
/// -
///
/// Set
clientExecutionTimeout to a value that allows at least one retry
/// to be processed after 5 seconds have elapsed since the first attempt for the TransactWriteItems
/// operation.
///
/// -
///
/// Set
socketTimeout to a value a little lower than the requestTimeout
/// setting.
///
/// -
///
///
requestTimeout should be set based on the time taken for the individual
/// retries of a single HTTP request for your use case, but setting it to 1 second or
/// higher should work well to reduce chances of retries and TransactionInProgressException
/// errors.
///
/// -
///
/// Use exponential backoff when retrying and tune backoff if needed.
///
///
///
/// Assuming default
/// retry policy, example timeout settings based on the guidelines above are as follows:
///
///
///
///
/// Example timeline:
///
/// -
///
/// 0-1000 first attempt
///
///
-
///
/// 1000-1500 first sleep/delay (default retry policy uses 500 ms as base delay for 4xx
/// errors)
///
///
-
///
/// 1500-2500 second attempt
///
///
-
///
/// 2500-3500 second sleep/delay (500 * 2, exponential backoff)
///
///
-
///
/// 3500-4500 third attempt
///
///
-
///
/// 4500-6500 third sleep/delay (500 * 2^2)
///
///
-
///
/// 6500-7500 fourth attempt (this can trigger inline recovery since 5 seconds have elapsed
/// since the first attempt reached TC)
///
///
///
/// REST API Reference for TransactWriteItems Operation
public virtual Task TransactWriteItemsAsync(TransactWriteItemsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = TransactWriteItemsRequestMarshaller.Instance;
options.ResponseUnmarshaller = TransactWriteItemsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = TransactWriteItemsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UntagResource
internal virtual UntagResourceResponse UntagResource(UntagResourceRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UntagResourceRequestMarshaller.Instance;
options.ResponseUnmarshaller = UntagResourceResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UntagResourceEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Removes the association of tags from an Amazon DynamoDB resource. You can call UntagResource
/// up to five times per second, per account.
///
///
///
/// For an overview on tagging DynamoDB resources, see Tagging
/// for DynamoDB in the Amazon DynamoDB Developer Guide.
///
///
/// Container for the necessary parameters to execute the UntagResource service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UntagResource service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for UntagResource Operation
public virtual Task UntagResourceAsync(UntagResourceRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UntagResourceRequestMarshaller.Instance;
options.ResponseUnmarshaller = UntagResourceResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UntagResourceEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateContinuousBackups
internal virtual UpdateContinuousBackupsResponse UpdateContinuousBackups(UpdateContinuousBackupsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateContinuousBackupsRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateContinuousBackupsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateContinuousBackupsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// UpdateContinuousBackups enables or disables point in time recovery for
/// the specified table. A successful UpdateContinuousBackups call returns
/// the current ContinuousBackupsDescription. Continuous backups are ENABLED
/// on all tables at table creation. If point in time recovery is enabled, PointInTimeRecoveryStatus
/// will be set to ENABLED.
///
///
///
/// Once continuous backups and point in time recovery are enabled, you can restore to
/// any point in time within EarliestRestorableDateTime and LatestRestorableDateTime.
///
///
///
///
/// LatestRestorableDateTime is typically 5 minutes before the current time.
/// You can restore your table to any point in time during the last 35 days.
///
///
/// Container for the necessary parameters to execute the UpdateContinuousBackups service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateContinuousBackups service method, as returned by DynamoDB.
///
/// Backups have not yet been enabled for this table.
///
///
/// An error occurred on the server side.
///
///
/// A source table with the name TableName does not currently exist within
/// the subscriber's account or the subscriber is operating in the wrong Amazon Web Services
/// Region.
///
/// REST API Reference for UpdateContinuousBackups Operation
public virtual Task UpdateContinuousBackupsAsync(UpdateContinuousBackupsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateContinuousBackupsRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateContinuousBackupsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateContinuousBackupsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateContributorInsights
internal virtual UpdateContributorInsightsResponse UpdateContributorInsights(UpdateContributorInsightsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateContributorInsightsRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateContributorInsightsResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Updates the status for contributor insights for a specific table or index. CloudWatch
/// Contributor Insights for DynamoDB graphs display the partition key and (if applicable)
/// sort key of frequently accessed items and frequently throttled items in plaintext.
/// If you require the use of Amazon Web Services Key Management Service (KMS) to encrypt
/// this table’s partition key and sort key data with an Amazon Web Services managed key
/// or customer managed key, you should not enable CloudWatch Contributor Insights for
/// DynamoDB for this table.
///
/// Container for the necessary parameters to execute the UpdateContributorInsights service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateContributorInsights service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for UpdateContributorInsights Operation
public virtual Task UpdateContributorInsightsAsync(UpdateContributorInsightsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateContributorInsightsRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateContributorInsightsResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateGlobalTable
internal virtual UpdateGlobalTableResponse UpdateGlobalTable(UpdateGlobalTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateGlobalTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateGlobalTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateGlobalTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Adds or removes replicas in the specified global table. The global table must already
/// exist to be able to use this operation. Any replica to be added must be empty, have
/// the same name as the global table, have the same key schema, have DynamoDB Streams
/// enabled, and have the same provisioned and maximum write capacity units.
///
///
///
/// This operation only applies to Version
/// 2017.11.29 (Legacy) of global tables. We recommend using Version
/// 2019.11.21 (Current) when creating new global tables, as it provides greater flexibility,
/// higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine
/// which version you are using, see Determining
/// the version. To update existing global tables from version 2017.11.29 (Legacy)
/// to version 2019.11.21 (Current), see
/// Updating global tables.
///
///
///
/// This operation only applies to Version
/// 2017.11.29 of global tables. If you are using global tables Version
/// 2019.11.21 you can use DescribeTable
/// instead.
///
///
///
/// Although you can use UpdateGlobalTable to add replicas and remove replicas
/// in a single request, for simplicity we recommend that you issue separate requests
/// for adding or removing replicas.
///
///
///
/// If global secondary indexes are specified, then the following conditions must also
/// be met:
///
/// -
///
/// The global secondary indexes must have the same name.
///
///
-
///
/// The global secondary indexes must have the same hash key and sort key (if present).
///
///
///
-
///
/// The global secondary indexes must have the same provisioned and maximum write capacity
/// units.
///
///
///
/// Container for the necessary parameters to execute the UpdateGlobalTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateGlobalTable service method, as returned by DynamoDB.
///
/// The specified global table does not exist.
///
///
/// An error occurred on the server side.
///
///
/// The specified replica is already part of the global table.
///
///
/// The specified replica is no longer part of the global table.
///
///
/// A source table with the name TableName does not currently exist within
/// the subscriber's account or the subscriber is operating in the wrong Amazon Web Services
/// Region.
///
/// REST API Reference for UpdateGlobalTable Operation
public virtual Task UpdateGlobalTableAsync(UpdateGlobalTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateGlobalTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateGlobalTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateGlobalTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateGlobalTableSettings
internal virtual UpdateGlobalTableSettingsResponse UpdateGlobalTableSettings(UpdateGlobalTableSettingsRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateGlobalTableSettingsRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateGlobalTableSettingsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateGlobalTableSettingsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Updates settings for a global table.
///
///
///
/// This operation only applies to Version
/// 2017.11.29 (Legacy) of global tables. We recommend using Version
/// 2019.11.21 (Current) when creating new global tables, as it provides greater flexibility,
/// higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine
/// which version you are using, see Determining
/// the version. To update existing global tables from version 2017.11.29 (Legacy)
/// to version 2019.11.21 (Current), see
/// Updating global tables.
///
///
///
/// Container for the necessary parameters to execute the UpdateGlobalTableSettings service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateGlobalTableSettings service method, as returned by DynamoDB.
///
/// The specified global table does not exist.
///
///
/// The operation tried to access a nonexistent index.
///
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The specified replica is no longer part of the global table.
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
/// REST API Reference for UpdateGlobalTableSettings Operation
public virtual Task UpdateGlobalTableSettingsAsync(UpdateGlobalTableSettingsRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateGlobalTableSettingsRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateGlobalTableSettingsResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateGlobalTableSettingsEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateItem
internal virtual UpdateItemResponse UpdateItem(UpdateItemRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Edits an existing item's attributes, or adds a new item to the table if it does not
/// already exist. You can put, delete, or add attribute values. You can also perform
/// a conditional update on an existing item (insert a new attribute name-value pair if
/// it doesn't exist, or replace an existing name-value pair if it has certain expected
/// attribute values).
///
///
///
/// You can also return the item's attribute values in the same UpdateItem
/// operation using the ReturnValues parameter.
///
///
/// The name of the table containing the item to update.
/// The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
/// This is a legacy parameter. Use UpdateExpression instead. For more information, see AttributeUpdates in the Amazon DynamoDB Developer Guide.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for UpdateItem Operation
public virtual Task UpdateItemAsync(string tableName, Dictionary key, Dictionary attributeUpdates, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new UpdateItemRequest();
request.TableName = tableName;
request.Key = key;
request.AttributeUpdates = attributeUpdates;
return UpdateItemAsync(request, cancellationToken);
}
///
/// Edits an existing item's attributes, or adds a new item to the table if it does not
/// already exist. You can put, delete, or add attribute values. You can also perform
/// a conditional update on an existing item (insert a new attribute name-value pair if
/// it doesn't exist, or replace an existing name-value pair if it has certain expected
/// attribute values).
///
///
///
/// You can also return the item's attribute values in the same UpdateItem
/// operation using the ReturnValues parameter.
///
///
/// The name of the table containing the item to update.
/// The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
/// This is a legacy parameter. Use UpdateExpression instead. For more information, see AttributeUpdates in the Amazon DynamoDB Developer Guide.
/// Use ReturnValues if you want to get the item attributes as they appear before or after they are successfully updated. For UpdateItem, the valid values are: -
NONE - If ReturnValues is not specified, or if its value is NONE, then nothing is returned. (This setting is the default for ReturnValues.) -
ALL_OLD - Returns all of the attributes of the item, as they appeared before the UpdateItem operation. -
UPDATED_OLD - Returns only the updated attributes, as they appeared before the UpdateItem operation. -
ALL_NEW - Returns all of the attributes of the item, as they appear after the UpdateItem operation. -
UPDATED_NEW - Returns only the updated attributes, as they appear after the UpdateItem operation.
There is no additional cost associated with requesting a return value aside from the small network and processing overhead of receiving a larger response. No read capacity units are consumed. The values returned are strongly consistent.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for UpdateItem Operation
public virtual Task UpdateItemAsync(string tableName, Dictionary key, Dictionary attributeUpdates, ReturnValue returnValues, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new UpdateItemRequest();
request.TableName = tableName;
request.Key = key;
request.AttributeUpdates = attributeUpdates;
request.ReturnValues = returnValues;
return UpdateItemAsync(request, cancellationToken);
}
///
/// Edits an existing item's attributes, or adds a new item to the table if it does not
/// already exist. You can put, delete, or add attribute values. You can also perform
/// a conditional update on an existing item (insert a new attribute name-value pair if
/// it doesn't exist, or replace an existing name-value pair if it has certain expected
/// attribute values).
///
///
///
/// You can also return the item's attribute values in the same UpdateItem
/// operation using the ReturnValues parameter.
///
///
/// Container for the necessary parameters to execute the UpdateItem service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateItem service method, as returned by DynamoDB.
///
/// A condition specified in the operation could not be evaluated.
///
///
/// An error occurred on the server side.
///
///
/// An item collection is too large. This exception is only returned for tables that have
/// one or more local secondary indexes.
///
///
/// Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically
/// retry requests that receive this exception. Your request is eventually successful,
/// unless your retry queue is too large to finish. Reduce the frequency of requests and
/// use exponential backoff. For more information, go to Error
/// Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
///
///
/// Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a
/// quota increase.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
///
/// Operation was rejected because there is an ongoing transaction for the item.
///
/// REST API Reference for UpdateItem Operation
public virtual Task UpdateItemAsync(UpdateItemRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateItemRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateItemResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateItemEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateTable
internal virtual UpdateTableResponse UpdateTable(UpdateTableRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB
/// Streams settings for a given table.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// You can only perform one of the following operations at once:
///
/// -
///
/// Modify the provisioned throughput settings of the table.
///
///
-
///
/// Remove a global secondary index from the table.
///
///
-
///
/// Create a new global secondary index on the table. After the index begins backfilling,
/// you can use
UpdateTable to perform other operations.
///
///
///
/// UpdateTable is an asynchronous operation; while it is executing, the
/// table status changes from ACTIVE to UPDATING. While it is
/// UPDATING, you cannot issue another UpdateTable request.
/// When the table returns to the ACTIVE state, the UpdateTable
/// operation is complete.
///
///
/// The name of the table to be updated.
/// The new provisioned throughput settings for the specified table or index.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for UpdateTable Operation
public virtual Task UpdateTableAsync(string tableName, ProvisionedThroughput provisionedThroughput, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var request = new UpdateTableRequest();
request.TableName = tableName;
request.ProvisionedThroughput = provisionedThroughput;
return UpdateTableAsync(request, cancellationToken);
}
///
/// Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB
/// Streams settings for a given table.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// You can only perform one of the following operations at once:
///
/// -
///
/// Modify the provisioned throughput settings of the table.
///
///
-
///
/// Remove a global secondary index from the table.
///
///
-
///
/// Create a new global secondary index on the table. After the index begins backfilling,
/// you can use
UpdateTable to perform other operations.
///
///
///
/// UpdateTable is an asynchronous operation; while it is executing, the
/// table status changes from ACTIVE to UPDATING. While it is
/// UPDATING, you cannot issue another UpdateTable request.
/// When the table returns to the ACTIVE state, the UpdateTable
/// operation is complete.
///
///
/// Container for the necessary parameters to execute the UpdateTable service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateTable service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for UpdateTable Operation
public virtual Task UpdateTableAsync(UpdateTableRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateTableRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateTableResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateTableEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateTableReplicaAutoScaling
internal virtual UpdateTableReplicaAutoScalingResponse UpdateTableReplicaAutoScaling(UpdateTableReplicaAutoScalingRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateTableReplicaAutoScalingRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateTableReplicaAutoScalingResponseUnmarshaller.Instance;
return Invoke(request, options);
}
///
/// Updates auto scaling settings on your global tables at once.
///
///
///
/// This operation only applies to Version
/// 2019.11.21 (Current) of global tables.
///
///
///
/// Container for the necessary parameters to execute the UpdateTableReplicaAutoScaling service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateTableReplicaAutoScaling service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for UpdateTableReplicaAutoScaling Operation
public virtual Task UpdateTableReplicaAutoScalingAsync(UpdateTableReplicaAutoScalingRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateTableReplicaAutoScalingRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateTableReplicaAutoScalingResponseUnmarshaller.Instance;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
#region UpdateTimeToLive
internal virtual UpdateTimeToLiveResponse UpdateTimeToLive(UpdateTimeToLiveRequest request)
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateTimeToLiveRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateTimeToLiveResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateTimeToLiveEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return Invoke(request, options);
}
///
/// The UpdateTimeToLive method enables or disables Time to Live (TTL) for
/// the specified table. A successful UpdateTimeToLive call returns the current
/// TimeToLiveSpecification. It can take up to one hour for the change to
/// fully process. Any additional UpdateTimeToLive calls for the same table
/// during this one hour duration result in a ValidationException.
///
///
///
/// TTL compares the current time in epoch time format to the time stored in the TTL attribute
/// of an item. If the epoch time value stored in the attribute is less than the current
/// time, the item is marked as expired and subsequently deleted.
///
///
///
/// The epoch time format is the number of seconds elapsed since 12:00:00 AM January
/// 1, 1970 UTC.
///
///
///
/// DynamoDB deletes expired items on a best-effort basis to ensure availability of throughput
/// for other data operations.
///
///
///
/// DynamoDB typically deletes expired items within two days of expiration. The exact
/// duration within which an item gets deleted after expiration is specific to the nature
/// of the workload. Items that have expired and not been deleted will still show up in
/// reads, queries, and scans.
///
///
///
/// As items are deleted, they are removed from any local secondary index and global secondary
/// index immediately in the same eventually consistent way as a standard delete operation.
///
///
///
/// For more information, see Time
/// To Live in the Amazon DynamoDB Developer Guide.
///
///
/// Container for the necessary parameters to execute the UpdateTimeToLive service method.
///
/// A cancellation token that can be used by other objects or threads to receive notice of cancellation.
///
///
/// The response from the UpdateTimeToLive service method, as returned by DynamoDB.
///
/// An error occurred on the server side.
///
///
/// There is no limit to the number of daily on-demand backups that can be taken.
///
///
///
/// For most purposes, up to 500 simultaneous table operations are allowed per account.
/// These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive,
/// RestoreTableFromBackup, and RestoreTableToPointInTime.
///
///
///
/// When you are creating a table with one or more secondary indexes, you can have up
/// to 250 such requests running at a time. However, if the table or index specifications
/// are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
///
///
///
/// When importing into DynamoDB, up to 50 simultaneous import table operations are allowed
/// per account.
///
///
///
/// There is a soft account quota of 2,500 tables.
///
///
///
/// GetRecords was called with a value of more than 1000 for the limit request parameter.
///
///
///
/// More than 2 processes are reading from the same streams shard at the same time. Exceeding
/// this limit may result in request throttling.
///
///
///
/// The operation conflicts with the resource's availability. For example, you attempted
/// to recreate an existing table, or tried to delete a table currently in the CREATING
/// state.
///
///
/// The operation tried to access a nonexistent table or index. The resource might not
/// be specified correctly, or its status might not be ACTIVE.
///
/// REST API Reference for UpdateTimeToLive Operation
public virtual Task UpdateTimeToLiveAsync(UpdateTimeToLiveRequest request, System.Threading.CancellationToken cancellationToken = default(CancellationToken))
{
var options = new InvokeOptions();
options.RequestMarshaller = UpdateTimeToLiveRequestMarshaller.Instance;
options.ResponseUnmarshaller = UpdateTimeToLiveResponseUnmarshaller.Instance;
options.EndpointDiscoveryMarshaller = UpdateTimeToLiveEndpointDiscoveryMarshaller.Instance;
options.EndpointOperation = EndpointOperation;
return InvokeAsync(request, options, cancellationToken);
}
#endregion
}
}