@aws-sdk/client-dynamodb 3.36.0 → 3.39.0

package/CHANGELOG.md

@@ -3,6 +3,48 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [3.39.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.38.0...v3.39.0) (2021-10-29)
+
+**Note:** Version bump only for package @aws-sdk/client-dynamodb
+
+
+
+
+
+# [3.38.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.37.0...v3.38.0) (2021-10-22)
+
+
+### Features
+
+* **client-documentation-generator:** rename package ([#2916](https://github.com/aws/aws-sdk-js-v3/issues/2916)) ([1a80bfd](https://github.com/aws/aws-sdk-js-v3/commit/1a80bfd2dfc583001ddb4a21b6432eaaad699aa7))
+* **clients:** export folder from index.ts ([#2912](https://github.com/aws/aws-sdk-js-v3/issues/2912)) ([183b46d](https://github.com/aws/aws-sdk-js-v3/commit/183b46dde7f5613128038bf1c076f3c0b693203b))
+
+
+
+
+
+# [3.37.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.36.1...v3.37.0) (2021-10-15)
+
+
+### Features
+
+* **clients:** update clients as of 10/15/2021 ([#2902](https://github.com/aws/aws-sdk-js-v3/issues/2902)) ([2730b54](https://github.com/aws/aws-sdk-js-v3/commit/2730b5424377944a5a2ad5e1ad7d3ca4135dae1c))
+
+
+
+
+
+## [3.36.1](https://github.com/aws/aws-sdk-js-v3/compare/v3.36.0...v3.36.1) (2021-10-12)
+
+
+### Bug Fixes
+
+* **clients:** emitDeclarationOnly in tsconfig.types.json ([#2893](https://github.com/aws/aws-sdk-js-v3/issues/2893)) ([6dc3d56](https://github.com/aws/aws-sdk-js-v3/commit/6dc3d56c20809c90cbdc4dd48627eeebc64af99d))
+
+
+
+
+
 # [3.36.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.35.0...v3.36.0) (2021-10-08)
 
 

package/dist-cjs/DynamoDB.js

@@ -52,27 +52,6 @@ const UpdateTableCommand_1 = require("./commands/UpdateTableCommand");
 const UpdateTableReplicaAutoScalingCommand_1 = require("./commands/UpdateTableReplicaAutoScalingCommand");
 const UpdateTimeToLiveCommand_1 = require("./commands/UpdateTimeToLiveCommand");
 const DynamoDBClient_1 = require("./DynamoDBClient");
-/**
- * <fullname>Amazon DynamoDB</fullname>
- *
- *
- *          <p>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.</p>
- *
- *          <p>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 AWS Management
- *       Console to monitor resource utilization and performance metrics.</p>
- *
- *          <p>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 AWS region, providing
- *       built-in high availability and data durability. </p>
- */
 class DynamoDB extends DynamoDBClient_1.DynamoDBClient {
     batchExecuteStatement(args, optionsOrCb, cb) {
         const command = new BatchExecuteStatementCommand_1.BatchExecuteStatementCommand(args);

package/dist-cjs/DynamoDBClient.js

@@ -12,27 +12,6 @@ const middleware_user_agent_1 = require("@aws-sdk/middleware-user-agent");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const DescribeEndpointsCommand_1 = require("./commands/DescribeEndpointsCommand");
 const runtimeConfig_1 = require("./runtimeConfig");
-/**
- * <fullname>Amazon DynamoDB</fullname>
- *
- *
- *          <p>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.</p>
- *
- *          <p>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 AWS Management
- *       Console to monitor resource utilization and performance metrics.</p>
- *
- *          <p>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 AWS region, providing
- *       built-in high availability and data durability. </p>
- */
 class DynamoDBClient extends smithy_client_1.Client {
     constructor(configuration) {
         const _config_0 = runtimeConfig_1.getRuntimeConfig(configuration);
@@ -54,11 +33,6 @@ class DynamoDBClient extends smithy_client_1.Client {
         this.middlewareStack.use(middleware_signing_1.getAwsAuthPlugin(this.config));
         this.middlewareStack.use(middleware_user_agent_1.getUserAgentPlugin(this.config));
     }
-    /**
-     * Destroy underlying resources, like sockets. It's usually not necessary to do this.
-     * However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed.
-     * Otherwise, sockets might stay open for quite a long time before the server terminates them.
-     */
     destroy() {
         super.destroy();
     }

package/dist-cjs/commands/BatchExecuteStatementCommand.js

@@ -5,37 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>
- * This operation allows you to perform batch reads and writes on data stored in DynamoDB, using PartiQL.
- * </p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, BatchExecuteStatementCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, BatchExecuteStatementCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new BatchExecuteStatementCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link BatchExecuteStatementCommandInput} for command's `input` shape.
- * @see {@link BatchExecuteStatementCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class BatchExecuteStatementCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/BatchGetItemCommand.js

@@ -5,80 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>The <code>BatchGetItem</code> operation returns the attributes of one or more items from one or
- *       more tables. You identify requested items by primary key.</p>
- *          <p>A single operation can retrieve up to 16 MB of data, which can contain as many as 100
- *             items. <code>BatchGetItem</code> returns a partial result if the response size limit is
- *             exceeded, the table's provisioned throughput is exceeded, or an internal processing
- *             failure occurs. If a partial result is returned, the operation returns a value for
- *                 <code>UnprocessedKeys</code>. You can use this value to retry the operation starting
- *             with the next item to get.</p>
- *          <important>
- *             <p>If you request more than 100 items, <code>BatchGetItem</code> returns a
- *                     <code>ValidationException</code> with the message "Too many items requested for
- *                 the BatchGetItem call."</p>
- *          </important>
- *          <p>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 <code>UnprocessedKeys</code> 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.</p>
- *          <p>If <i>none</i> of the items can be processed due to insufficient
- *             provisioned throughput on all of the tables in the request, then
- *                 <code>BatchGetItem</code> returns a
- *                 <code>ProvisionedThroughputExceededException</code>. If <i>at least
- *                 one</i> of the items is successfully processed, then
- *                 <code>BatchGetItem</code> completes successfully, while returning the keys of the
- *             unread items in <code>UnprocessedKeys</code>.</p>
- *          <important>
- *             <p>If DynamoDB returns any unprocessed items, you should retry the batch operation on those
- *         items. However, <i>we strongly recommend that you use an exponential backoff algorithm</i>.
- *         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.</p>
- *             <p>For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations">Batch
- *           Operations and Error Handling</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
- *          </important>
- *          <p>By default, <code>BatchGetItem</code> performs eventually consistent reads on every table in the
- *       request. If you want strongly consistent reads instead, you can set <code>ConsistentRead</code> to
- *         <code>true</code> for any or all tables.</p>
- *          <p>In order to minimize response latency, <code>BatchGetItem</code> retrieves items in parallel.</p>
- *          <p>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 <code>ProjectionExpression</code> parameter.</p>
- *          <p>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 <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#CapacityUnitCalculations">Working with Tables</a> in the <i>Amazon DynamoDB Developer
- *                 Guide</i>.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, BatchGetItemCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, BatchGetItemCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new BatchGetItemCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link BatchGetItemCommandInput} for command's `input` shape.
- * @see {@link BatchGetItemCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class BatchGetItemCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/BatchWriteItemCommand.js

@@ -5,109 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>The <code>BatchWriteItem</code> operation puts or deletes multiple items in one or more
- *             tables. A single call to <code>BatchWriteItem</code> can write up to 16 MB of data,
- *             which can comprise as many as 25 put or delete requests. Individual items to be written
- *             can be as large as 400 KB.</p>
- *          <note>
- *             <p>
- *                <code>BatchWriteItem</code> cannot update items. To update items, use the <code>UpdateItem</code>
- *         action.</p>
- *          </note>
- *          <p>The individual <code>PutItem</code> and <code>DeleteItem</code> operations specified in
- *         <code>BatchWriteItem</code> are atomic; however <code>BatchWriteItem</code> 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
- *         <code>UnprocessedItems</code> response parameter. You can investigate and optionally resend the
- *       requests. Typically, you would call <code>BatchWriteItem</code> in a loop. Each iteration would
- *       check for unprocessed items and submit a new <code>BatchWriteItem</code> request with those
- *       unprocessed items until all items have been processed.</p>
- *          <p>If <i>none</i> of the items can be processed due to insufficient
- *             provisioned throughput on all of the tables in the request, then
- *                 <code>BatchWriteItem</code> returns a
- *                 <code>ProvisionedThroughputExceededException</code>.</p>
- *          <important>
- *             <p>If DynamoDB returns any unprocessed items, you should retry the batch operation on those
- *         items. However, <i>we strongly recommend that you use an exponential backoff algorithm</i>.
- *         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.</p>
- *             <p>For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#Programming.Errors.BatchOperations">Batch Operations and Error Handling</a> in the <i>Amazon DynamoDB
- *                     Developer Guide</i>.</p>
- *          </important>
- *
- *          <p>With <code>BatchWriteItem</code>, 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,
- *                 <code>BatchWriteItem</code> does not behave in the same way as individual
- *                 <code>PutItem</code> and <code>DeleteItem</code> calls would. For example, you
- *             cannot specify conditions on individual put and delete requests, and
- *                 <code>BatchWriteItem</code> does not return deleted items in the response.</p>
- *          <p>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, <code>BatchWriteItem</code>
- *       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.</p>
- *          <p>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.</p>
- *          <p>If one or more of the following is true, DynamoDB rejects the entire batch write operation:</p>
- *          <ul>
- *             <li>
- *                <p>One or more tables specified in the <code>BatchWriteItem</code> request does not exist.</p>
- *             </li>
- *             <li>
- *                <p>Primary key attributes specified on an item in the request do not match those in the corresponding table's primary key schema.</p>
- *             </li>
- *             <li>
- *                <p>You try to perform multiple operations on the same item in the same <code>BatchWriteItem</code>
- *           request. For example, you cannot put and delete the same item in the same
- *             <code>BatchWriteItem</code> request. </p>
- *             </li>
- *             <li>
- * 	              <p>
- * 		Your request contains at least two items with identical hash and range keys (which essentially is two put operations).
- * 	    </p>
- *     	       </li>
- *             <li>
- *                <p>There are more than 25 requests in the batch.</p>
- *             </li>
- *             <li>
- *                <p>Any individual item in a batch exceeds 400 KB.</p>
- *             </li>
- *             <li>
- *                <p>The total request size exceeds 16 MB.</p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, BatchWriteItemCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, BatchWriteItemCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new BatchWriteItemCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link BatchWriteItemCommandInput} for command's `input` shape.
- * @see {@link BatchWriteItemCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class BatchWriteItemCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/CreateBackupCommand.js

@@ -5,64 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>Creates a backup for an existing table.</p>
- *          <p> 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. </p>
- *          <p> 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. </p>
- *          <p>You can call <code>CreateBackup</code> at a maximum rate of 50 times per second.</p>
- *          <p>All backups in DynamoDB work without consuming any provisioned throughput on the table.</p>
- *          <p> 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. </p>
- *          <p>
- *              Along with data, the following are also included on the backups:
- *          </p>
- *            <ul>
- *             <li>
- *                   <p>Global secondary indexes (GSIs)</p>
- *               </li>
- *             <li>
- *                   <p>Local secondary indexes (LSIs)</p>
- *               </li>
- *             <li>
- *                   <p>Streams</p>
- *               </li>
- *             <li>
- *                   <p>Provisioned read and write capacity</p>
- *               </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, CreateBackupCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, CreateBackupCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new CreateBackupCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateBackupCommandInput} for command's `input` shape.
- * @see {@link CreateBackupCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateBackupCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/CreateGlobalTableCommand.js

@@ -5,102 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>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. </p>
- *          <note>
- *             <p>This operation only applies to <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html">Version 2017.11.29</a> of global tables.</p>
- *          </note>
- *
- *          <p>If you want to add a new replica table to a global table, each of the following conditions
- *    must be true:</p>
- *          <ul>
- *             <li>
- *                <p>The table must have the same primary key as all of the other replicas.</p>
- *             </li>
- *             <li>
- *                <p>The table must have the same name as all of the other replicas.</p>
- *             </li>
- *             <li>
- *                <p>The table must have DynamoDB Streams enabled, with the stream containing both the new and the old
- *      images of the item.</p>
- *             </li>
- *             <li>
- *                <p>None of the replica tables in the global table can contain any data.</p>
- *             </li>
- *          </ul>
- *          <p>
- *      If global secondary indexes are specified, then the following conditions must also be met:
- *    </p>
- *         <ul>
- *             <li>
- *                <p>
- *                The global secondary indexes must have the same name.
- *             </p>
- *             </li>
- *             <li>
- *                <p>
- *                The global secondary indexes must have the same hash key and sort key (if present).
- *             </p>
- *             </li>
- *          </ul>
- *          <p>
- *      If local secondary indexes are specified, then the following conditions must also be met:
- *    </p>
- *         <ul>
- *             <li>
- *                <p>
- *                The local secondary indexes must have the same name.
- *             </p>
- *             </li>
- *             <li>
- *                <p>
- *                The local secondary indexes must have the same hash key and sort key (if present).
- *             </p>
- *             </li>
- *          </ul>
- *
- *          <important>
- *             <p>
- *        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.
- *     </p>
- *             <p>
- *        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.
- *     </p>
- *          </important>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, CreateGlobalTableCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, CreateGlobalTableCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new CreateGlobalTableCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateGlobalTableCommandInput} for command's `input` shape.
- * @see {@link CreateGlobalTableCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateGlobalTableCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/CreateTableCommand.js

@@ -5,47 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>The <code>CreateTable</code> operation adds a new table to your account. In an AWS
- *             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.</p>
- *          <p>
- *             <code>CreateTable</code> is an asynchronous operation. Upon receiving a <code>CreateTable</code> request,
- *       DynamoDB immediately returns a response with a <code>TableStatus</code> of <code>CREATING</code>. After
- *       the table is created, DynamoDB sets the <code>TableStatus</code> to <code>ACTIVE</code>. You can
- *       perform read and write operations only on an <code>ACTIVE</code> table. </p>
- *          <p>You can optionally define secondary indexes on the new table, as part of the <code>CreateTable</code>
- *       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 <code>CREATING</code> state at
- *       any given time.</p>
- *          <p>You can use the <code>DescribeTable</code> action to check the table status.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, CreateTableCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, CreateTableCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new CreateTableCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateTableCommandInput} for command's `input` shape.
- * @see {@link CreateTableCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateTableCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/DeleteBackupCommand.js

@@ -5,36 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>Deletes an existing backup of a table.</p>
- *          <p>You can call <code>DeleteBackup</code> at a maximum rate of 10 times per second.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, DeleteBackupCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, DeleteBackupCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new DeleteBackupCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteBackupCommandInput} for command's `input` shape.
- * @see {@link DeleteBackupCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class DeleteBackupCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/DeleteItemCommand.js

@@ -5,40 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_0_1 = require("../protocols/Aws_json1_0");
-/**
- * <p>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.</p>
- *          <p>In addition to deleting an item, you can also return the item's attribute values in the same
- *       operation, using the <code>ReturnValues</code> parameter.</p>
- *          <p>Unless you specify conditions, the <code>DeleteItem</code> is an idempotent operation; running it
- *       multiple times on the same item or attribute does <i>not</i> result in an error response.</p>
- *          <p>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.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { DynamoDBClient, DeleteItemCommand } from "@aws-sdk/client-dynamodb"; // ES Modules import
- * // const { DynamoDBClient, DeleteItemCommand } = require("@aws-sdk/client-dynamodb"); // CommonJS import
- * const client = new DynamoDBClient(config);
- * const command = new DeleteItemCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteItemCommandInput} for command's `input` shape.
- * @see {@link DeleteItemCommandOutput} for command's `response` shape.
- * @see {@link DynamoDBClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class DeleteItemCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);