@aws-sdk/client-dynamodb 3.31.0 → 3.35.0

package/commands/BatchGetItemCommand.ts

@@ -1,139 +0,0 @@
-import { DynamoDBClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../DynamoDBClient";
-import { BatchGetItemInput, BatchGetItemOutput } from "../models/models_0";
-import {
-  deserializeAws_json1_0BatchGetItemCommand,
-  serializeAws_json1_0BatchGetItemCommand,
-} from "../protocols/Aws_json1_0";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-export interface BatchGetItemCommandInput extends BatchGetItemInput {}
-export interface BatchGetItemCommandOutput extends BatchGetItemOutput, __MetadataBearer {}
-
-/**
- * <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.
- *
- */
-export class BatchGetItemCommand extends $Command<
-  BatchGetItemCommandInput,
-  BatchGetItemCommandOutput,
-  DynamoDBClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: BatchGetItemCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: DynamoDBClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<BatchGetItemCommandInput, BatchGetItemCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "DynamoDBClient";
-    const commandName = "BatchGetItemCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: BatchGetItemInput.filterSensitiveLog,
-      outputFilterSensitiveLog: BatchGetItemOutput.filterSensitiveLog,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: BatchGetItemCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_json1_0BatchGetItemCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<BatchGetItemCommandOutput> {
-    return deserializeAws_json1_0BatchGetItemCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}

package/commands/BatchWriteItemCommand.ts

@@ -1,168 +0,0 @@
-import { DynamoDBClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../DynamoDBClient";
-import { BatchWriteItemInput, BatchWriteItemOutput } from "../models/models_0";
-import {
-  deserializeAws_json1_0BatchWriteItemCommand,
-  serializeAws_json1_0BatchWriteItemCommand,
-} from "../protocols/Aws_json1_0";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-export interface BatchWriteItemCommandInput extends BatchWriteItemInput {}
-export interface BatchWriteItemCommandOutput extends BatchWriteItemOutput, __MetadataBearer {}
-
-/**
- * <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.
- *
- */
-export class BatchWriteItemCommand extends $Command<
-  BatchWriteItemCommandInput,
-  BatchWriteItemCommandOutput,
-  DynamoDBClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: BatchWriteItemCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: DynamoDBClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<BatchWriteItemCommandInput, BatchWriteItemCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "DynamoDBClient";
-    const commandName = "BatchWriteItemCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: BatchWriteItemInput.filterSensitiveLog,
-      outputFilterSensitiveLog: BatchWriteItemOutput.filterSensitiveLog,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: BatchWriteItemCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_json1_0BatchWriteItemCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<BatchWriteItemCommandOutput> {
-    return deserializeAws_json1_0BatchWriteItemCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}

package/commands/CreateBackupCommand.ts

@@ -1,123 +0,0 @@
-import { DynamoDBClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../DynamoDBClient";
-import { CreateBackupInput, CreateBackupOutput } from "../models/models_0";
-import {
-  deserializeAws_json1_0CreateBackupCommand,
-  serializeAws_json1_0CreateBackupCommand,
-} from "../protocols/Aws_json1_0";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-export interface CreateBackupCommandInput extends CreateBackupInput {}
-export interface CreateBackupCommandOutput extends CreateBackupOutput, __MetadataBearer {}
-
-/**
- * <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.
- *
- */
-export class CreateBackupCommand extends $Command<
-  CreateBackupCommandInput,
-  CreateBackupCommandOutput,
-  DynamoDBClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: CreateBackupCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: DynamoDBClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<CreateBackupCommandInput, CreateBackupCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "DynamoDBClient";
-    const commandName = "CreateBackupCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: CreateBackupInput.filterSensitiveLog,
-      outputFilterSensitiveLog: CreateBackupOutput.filterSensitiveLog,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: CreateBackupCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_json1_0CreateBackupCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<CreateBackupCommandOutput> {
-    return deserializeAws_json1_0CreateBackupCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}

package/commands/CreateGlobalTableCommand.ts

@@ -1,161 +0,0 @@
-import { DynamoDBClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../DynamoDBClient";
-import { CreateGlobalTableInput, CreateGlobalTableOutput } from "../models/models_0";
-import {
-  deserializeAws_json1_0CreateGlobalTableCommand,
-  serializeAws_json1_0CreateGlobalTableCommand,
-} from "../protocols/Aws_json1_0";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-export interface CreateGlobalTableCommandInput extends CreateGlobalTableInput {}
-export interface CreateGlobalTableCommandOutput extends CreateGlobalTableOutput, __MetadataBearer {}
-
-/**
- * <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.
- *
- */
-export class CreateGlobalTableCommand extends $Command<
-  CreateGlobalTableCommandInput,
-  CreateGlobalTableCommandOutput,
-  DynamoDBClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: CreateGlobalTableCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: DynamoDBClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<CreateGlobalTableCommandInput, CreateGlobalTableCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "DynamoDBClient";
-    const commandName = "CreateGlobalTableCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: CreateGlobalTableInput.filterSensitiveLog,
-      outputFilterSensitiveLog: CreateGlobalTableOutput.filterSensitiveLog,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: CreateGlobalTableCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_json1_0CreateGlobalTableCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<CreateGlobalTableCommandOutput> {
-    return deserializeAws_json1_0CreateGlobalTableCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}