aws-sdk-core 2.0.0.rc14 → 2.0.0.rc15

data/apis/dynamodb-2011-12-05.waiters.json

@@ -1,27 +0,0 @@
-{
-  "waiters": {
-    "__default__": {
-      "interval": 20,
-      "max_attempts": 25
-    },
-    "__TableState": {
-      "operation": "DescribeTable"
-    },
-    "TableExists": {
-      "extends": "__TableState",
-      "description": "Wait until a table exists and can be accessed",
-      "ignore_errors": [
-        "ResourceNotFoundException"
-      ],
-      "success_type": "output",
-      "success_path": "Table.TableStatus",
-      "success_value": "ACTIVE"
-    },
-    "TableNotExists": {
-      "extends": "__TableState",
-      "description": "Wait until a table is deleted",
-      "success_type": "error",
-      "success_value": "ResourceNotFoundException"
-    }
-  }
-}

data/apis/dynamodb-2012-08-10.api.json

@@ -1,1857 +0,0 @@
-{
-  "metadata":{
-    "apiVersion":"2012-08-10",
-    "endpointPrefix":"dynamodb",
-    "jsonVersion":"1.0",
-    "serviceAbbreviation":"DynamoDB",
-    "serviceFullName":"Amazon DynamoDB",
-    "signatureVersion":"v4",
-    "targetPrefix":"DynamoDB_20120810",
-    "protocol":"json"
-  },
-  "documentation":"<fullname>Amazon DynamoDB</fullname> <b>Overview</b> <p>This is the Amazon DynamoDB API Reference. This guide provides descriptions and samples of the low-level DynamoDB API. For information about DynamoDB application development, go to the <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/\">Amazon DynamoDB Developer Guide</a>.</p> <p>Instead of making the requests to the low-level DynamoDB API directly from your application, we recommend that you use the AWS Software Development Kits (SDKs). The easy-to-use libraries in the AWS SDKs make it unnecessary to call the low-level DynamoDB API directly from your application. The libraries take care of request authentication, serialization, and connection management. For more information, go to <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/UsingAWSSDK.html\">Using the AWS SDKs with DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> <p>If you decide to code against the low-level DynamoDB API directly, you will need to write the necessary code to authenticate your requests. For more information on signing your requests, go to <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/API.html\">Using the DynamoDB API</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> <p>The following are short descriptions of each low-level API action, organized by function.</p> <p> <b>Managing Tables</b> </p> <p> <ul> <li> <p><i>CreateTable</i> - Creates a table with user-specified provisioned throughput settings. You must designate one attribute as the hash primary key for the table; you can optionally designate a second attribute as the range primary key. DynamoDB creates indexes on these key attributes for fast data access. Optionally, you can create one or more secondary indexes, which provide fast data access using non-key attributes.</p> </li> <li> <p><i>DescribeTable</i> - Returns metadata for a table, such as table size, status, and index information.</p> </li> <li> <p><i>UpdateTable</i> - Modifies the provisioned throughput settings for a table. Optionally, you can modify the provisioned throughput settings for global secondary indexes on the table.</p> </li> <li> <p><i>ListTables</i> - Returns a list of all tables associated with the current AWS account and endpoint.</p> </li> <li> <p><i>DeleteTable</i> - Deletes a table and all of its indexes.</p> </li> </ul> </p> <p>For conceptual information about managing tables, go to <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html\">Working with Tables</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> <p> <b>Reading Data</b> </p> <p> <ul> <li> <p><i>GetItem</i> - Returns a set of attributes for the item that has a given primary key. By default, <i>GetItem</i> performs an eventually consistent read; however, applications can specify a strongly consistent read instead.</p> </li> <li> <p><i>BatchGetItem</i> - Performs multiple <i>GetItem</i> requests for data items using their primary keys, from one table or multiple tables. The response from <i>BatchGetItem</i> has a size limit of 1 MB and returns a maximum of 100 items. Both eventually consistent and strongly consistent reads can be used.</p> </li> <li> <p><i>Query</i> - Returns one or more items from a table or a secondary index. You must provide a specific hash key value. You can narrow the scope of the query using comparison operators against a range key value, or on the index key. <i>Query</i> supports either eventual or strong consistency. A single response has a size limit of 1 MB.</p> </li> <li> <p><i>Scan</i> - Reads every item in a table; the result set is eventually consistent. You can limit the number of items returned by filtering the data attributes, using conditional expressions. <i>Scan</i> can be used to enable ad-hoc querying of a table against non-key attributes; however, since this is a full table scan without using an index, <i>Scan</i> should not be used for any application query use case that requires predictable performance.</p> </li> </ul> </p> <p>For conceptual information about reading data, go to <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html\">Working with Items</a> and <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html\">Query and Scan Operations</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> <p> <b>Modifying Data</b> </p> <p> <ul> <li> <p><i>PutItem</i> - Creates a new item, or replaces an existing item with a new item (including all the attributes). By default, if an item in the table already exists with the same primary key, the new item completely replaces the existing item. You can use conditional operators to replace an item only if its attribute values match certain conditions, or to insert a new item only if that item doesn't already exist.</p> </li> <li> <p><i>UpdateItem</i> - Modifies the attributes of an existing item. You can also use conditional operators to perform an update only if the item's attribute values match certain conditions.</p> </li> <li> <p><i>DeleteItem</i> - Deletes an item in a table by primary key. You can use conditional operators to perform a delete an item only if the item's attribute values match certain conditions.</p> </li> <li> <p><i>BatchWriteItem</i> - Performs multiple <i>PutItem</i> and <i>DeleteItem</i> requests across multiple tables in a single request. A failure of any request(s) in the batch will not cause the entire <i>BatchWriteItem</i> operation to fail. Supports batches of up to 25 items to put or delete, with a maximum total request size of 1 MB. </p> </li> </ul> </p> <p>For conceptual information about modifying data, go to <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html\">Working with Items</a> and <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html\">Query and Scan Operations</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
-  "operations":{
-    "BatchGetItem":{
-      "name":"BatchGetItem",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"BatchGetItemInput",
-        "documentation":"<p>Represents the input of a <i>BatchGetItem</i> operation.</p>"
-      },
-      "output":{
-        "shape":"BatchGetItemOutput",
-        "documentation":"<p>Represents the output of a <i>BatchGetItem</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>The <i>BatchGetItem</i> 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 1 MB of data, which can contain as many as 100 items. <i>BatchGetItem</i> will return 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 <i>UnprocessedKeys</i>. You can use this value to retry the operation starting with the next item to get.</p> <p>For example, if you ask to retrieve 100 items, but each individual item is 50 KB in size, the system returns 20 items (1 MB) and an appropriate <i>UnprocessedKeys</i> 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 <i>BatchGetItem</i> will throw a <i>ProvisionedThroughputExceededException</i>. If <i>at least one</i> of the items is successfully processed, then <i>BatchGetItem</i> completes successfully, while returning the keys of the unread items in <i>UnprocessedKeys</i>.</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, go to <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations\">Batch Operations and Error Handling</a> in the Amazon DynamoDB Developer Guide.</p></important> <p>By default, <i>BatchGetItem</i> performs eventually consistent reads on every table in the request. If you want strongly consistent reads instead, you can set <i>ConsistentRead</i> to <code>true</code> for any or all tables.</p> <p>In order to minimize response latency, <i>BatchGetItem</i> retrieves items in parallel.</p> <p>When designing your application, keep in mind that DynamoDB does not return attributes in any particular order. To help parse the response by item, include the primary key values for the items in your request in the <i>AttributesToGet</i> 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=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#CapacityUnitCalculations\">Capacity Units Calculations</a> in the Amazon DynamoDB Developer Guide.</p>"
-    },
-    "BatchWriteItem":{
-      "name":"BatchWriteItem",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"BatchWriteItemInput",
-        "documentation":"<p>Represents the input of a <i>BatchWriteItem</i> operation.</p>"
-      },
-      "output":{
-        "shape":"BatchWriteItemOutput",
-        "documentation":"<p>Represents the output of a <i>BatchWriteItem</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"ItemCollectionSizeLimitExceededException",
-          "exception":true,
-          "documentation":"<p>An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>The <i>BatchWriteItem</i> operation puts or deletes multiple items in one or more tables. A single call to <i>BatchWriteItem</i> can write up to 1 MB of data, which can comprise as many as 25 put or delete requests. Individual items to be written can be as large as 64 KB.</p> <p>The individual <i>PutItem</i> and <i>DeleteItem</i> operations specified in <i>BatchWriteItem</i> are atomic; however <i>BatchWriteItem</i> 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 <i>UnprocessedItems</i> response parameter. You can investigate and optionally resend the requests. Typically, you would call <i>BatchWriteItem</i> in a loop. Each iteration would check for unprocessed items and submit a new <i>BatchWriteItem</i> request with those unprocessed items until all items have been processed.</p> <p>Note that if <i>none</i> of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then <i>BatchGetItem</i> will throw a <i>ProvisionedThroughputExceededException</i>.</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, go to <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations\">Batch Operations and Error Handling</a> in the Amazon DynamoDB Developer Guide.</p></important> <p>With <i>BatchWriteItem</i>, you can efficiently write or delete large amounts of data, such as from Amazon Elastic MapReduce (EMR), or copy data from another database into DynamoDB. In order to improve performance with these large-scale operations, <i>BatchWriteItem</i> does not behave in the same way as individual <i>PutItem</i> and <i>DeleteItem</i> calls would For example, you cannot specify conditions on individual put and delete requests, and <i>BatchWriteItem</i> does not return deleted items in the response.</p> <p>If you use a programming language that supports concurrency, such as Java, 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, such as PHP, you must update or delete the specified items one at a time. In both situations, <i>BatchWriteItem</i> provides an alternative where the API 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 <i>BatchWriteItem</i> 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 <i>BatchWriteItem</i> request. For example, you cannot put and delete the same item in the same <i>BatchWriteItem</i> request. </p> </li> <li> <p>The total request size exceeds 1 MB.</p> </li> <li> <p>Any individual item in a batch exceeds 64 KB.</p> </li> </ul>"
-    },
-    "CreateTable":{
-      "name":"CreateTable",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"CreateTableInput",
-        "documentation":"<p>Represents the input of a <i>CreateTable</i> operation.</p>"
-      },
-      "output":{
-        "shape":"CreateTableOutput",
-        "documentation":"<p>Represents the output of a <i>CreateTable</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ResourceInUseException",
-          "exception":true,
-          "documentation":"<p>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 <code>CREATING</code> state.</p>"
-        },
-        {
-          "shape":"LimitExceededException",
-          "exception":true,
-          "documentation":"<p>The number of concurrent table requests (cumulative number of tables in the <code>CREATING</code>, <code>DELETING</code> or <code>UPDATING</code> state) exceeds the maximum allowed of 10.</p> <p>Also, for tables with secondary indexes, only one of those tables can be in the <code>CREATING</code> state at any point in time. Do not attempt to create more than one such table simultaneously.</p> <p>The total limit of tables in the <code>ACTIVE</code> state is 250.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>The <i>CreateTable</i> 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><i>CreateTable</i> is an asynchronous operation. Upon receiving a <i>CreateTable</i> request, DynamoDB immediately returns a response with a <i>TableStatus</i> of <code>CREATING</code>. After the table is created, DynamoDB sets the <i>TableStatus</i> to <code>ACTIVE</code>. You can perform read and write operations only on an <code>ACTIVE</code> table. </p> <p>If you want to create multiple tables with secondary indexes on them, you must create them 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 <i>DescribeTable</i> API to check the table status.</p>"
-    },
-    "DeleteItem":{
-      "name":"DeleteItem",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"DeleteItemInput",
-        "documentation":"<p>Represents the input of a <i>DeleteItem</i> operation.</p>"
-      },
-      "output":{
-        "shape":"DeleteItemOutput",
-        "documentation":"<p>Represents the output of a <i>DeleteItem</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ConditionalCheckFailedException",
-          "exception":true,
-          "documentation":"<p>A condition specified in the operation could not be evaluated.</p>"
-        },
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"ItemCollectionSizeLimitExceededException",
-          "exception":true,
-          "documentation":"<p>An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<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 <i>ReturnValues</i> parameter.</p> <p>Unless you specify conditions, the <i>DeleteItem</i> 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 only deleting items if specific conditions are met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item is not deleted. </p>"
-    },
-    "DeleteTable":{
-      "name":"DeleteTable",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"DeleteTableInput",
-        "documentation":"<p>Represents the input of a <i>DeleteTable</i> operation.</p>"
-      },
-      "output":{
-        "shape":"DeleteTableOutput",
-        "documentation":"<p>Represents the output of a <i>DeleteTable</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ResourceInUseException",
-          "exception":true,
-          "documentation":"<p>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 <code>CREATING</code> state.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"LimitExceededException",
-          "exception":true,
-          "documentation":"<p>The number of concurrent table requests (cumulative number of tables in the <code>CREATING</code>, <code>DELETING</code> or <code>UPDATING</code> state) exceeds the maximum allowed of 10.</p> <p>Also, for tables with secondary indexes, only one of those tables can be in the <code>CREATING</code> state at any point in time. Do not attempt to create more than one such table simultaneously.</p> <p>The total limit of tables in the <code>ACTIVE</code> state is 250.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>The <i>DeleteTable</i> operation deletes a table and all of its items. After a <i>DeleteTable</i> request, the specified table is in the <code>DELETING</code> state until DynamoDB completes the deletion. If the table is in the <code>ACTIVE</code> state, you can delete it. If a table is in <code>CREATING</code> or <code>UPDATING</code> states, then DynamoDB returns a <i>ResourceInUseException</i>. If the specified table does not exist, DynamoDB returns a <i>ResourceNotFoundException</i>. If table is already in the <code>DELETING</code> state, no error is returned. </p> <p>When you delete a table, any indexes on that table are also deleted.</p> <p>Use the <i>DescribeTable</i> API to check the status of the table. </p>"
-    },
-    "DescribeTable":{
-      "name":"DescribeTable",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"DescribeTableInput",
-        "documentation":"<p>Represents the input of a <i>DescribeTable</i> operation.</p>"
-      },
-      "output":{
-        "shape":"DescribeTableOutput",
-        "documentation":"<p>Represents the output of a <i>DescribeTable</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>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.</p>"
-    },
-    "GetItem":{
-      "name":"GetItem",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"GetItemInput",
-        "documentation":"<p>Represents the input of a <i>GetItem</i> operation.</p>"
-      },
-      "output":{
-        "shape":"GetItemOutput",
-        "documentation":"<p>Represents the output of a <i>GetItem</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>The <i>GetItem</i> operation returns a set of attributes for the item with the given primary key. If there is no matching item, <i>GetItem</i> does not return any data.</p> <p><i>GetItem</i> provides an eventually consistent read by default. If your application requires a strongly consistent read, set <i>ConsistentRead</i> to <code>true</code>. Although a strongly consistent read might take more time than an eventually consistent read, it always returns the last updated value.</p>"
-    },
-    "ListTables":{
-      "name":"ListTables",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"ListTablesInput",
-        "documentation":"<p>Represents the input of a <i>ListTables</i> operation.</p>"
-      },
-      "output":{
-        "shape":"ListTablesOutput",
-        "documentation":"<p>Represents the output of a <i>ListTables</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>Returns an array of table names associated with the current account and endpoint. The output from <i>ListTables</i> is paginated, with each page returning a maximum of 100 table names.</p>"
-    },
-    "PutItem":{
-      "name":"PutItem",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"PutItemInput",
-        "documentation":"<p>Represents the input of a <i>PutItem</i> operation.</p>"
-      },
-      "output":{
-        "shape":"PutItemOutput",
-        "documentation":"<p>Represents the output of a <i>PutItem</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ConditionalCheckFailedException",
-          "exception":true,
-          "documentation":"<p>A condition specified in the operation could not be evaluated.</p>"
-        },
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"ItemCollectionSizeLimitExceededException",
-          "exception":true,
-          "documentation":"<p>An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>Creates a new item, or replaces an old item with a new item. If an item already exists in the specified table with the same primary key, the new item completely replaces the existing item. You can perform a conditional put (insert a new item if one with the specified primary key doesn't exist), or replace an existing item if it has certain attribute values. </p> <p>In addition to putting an item, you can also return the item's attribute values in the same operation, using the <i>ReturnValues</i> parameter.</p> <p>When you add an item, the primary key attribute(s) are the only required attributes. Attribute values cannot be null. String and binary type attributes must have lengths greater than zero. Set type attributes cannot be empty. Requests with empty values will be rejected with a <i>ValidationException</i>.</p> <p>You can request that <i>PutItem</i> return either a copy of the old item (before the update) or a copy of the new item (after the update). For more information, see the <i>ReturnValues</i> description.</p> <p>For more information about using this API, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html\">Working with Items</a> in the Amazon DynamoDB Developer Guide.</p>"
-    },
-    "Query":{
-      "name":"Query",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"QueryInput",
-        "documentation":"<p>Represents the input of a <i>Query</i> operation.</p>"
-      },
-      "output":{
-        "shape":"QueryOutput",
-        "documentation":"<p>Represents the output of a <i>Query</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>A <i>Query</i> operation directly accesses items from a table using the table primary key, or from an index using the index key. You must provide a specific hash key value. You can narrow the scope of the query by using comparison operators on the range key value, or on the index key. You can use the <i>ScanIndexForward</i> parameter to get results in forward or reverse order, by range key or by index key. </p> <p>Queries that do not return results consume the minimum read capacity units according to the type of read.</p> <p>If the total number of items meeting the query criteria exceeds the result set size limit of 1 MB, the query stops and results are returned to the user with a <i>LastEvaluatedKey</i> to continue the query in a subsequent operation. Unlike a <i>Scan</i> operation, a <i>Query</i> operation never returns an empty result set <i>and</i> a <i>LastEvaluatedKey</i>. The <i>LastEvaluatedKey</i> is only provided if the results exceed 1 MB, or if you have used <i>Limit</i>. </p> <p>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 <i>ConsistentRead</i> to true and obtain a strongly consistent result. Global secondary indexes support eventually consistent reads only, so do not specify <i>ConsistentRead</i> when querying a global secondary index.</p>"
-    },
-    "Scan":{
-      "name":"Scan",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"ScanInput",
-        "documentation":"<p>Represents the input of a <i>Scan</i> operation.</p>"
-      },
-      "output":{
-        "shape":"ScanOutput",
-        "documentation":"<p>Represents the output of a <i>Scan</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>The <i>Scan</i> operation returns one or more items and item attributes by accessing every item in the table. To have DynamoDB return fewer items, you can provide a <i>ScanFilter</i>.</p> <p>If the total number of scanned items exceeds the maximum data set size limit of 1 MB, the scan stops and results are returned to the user with a <i>LastEvaluatedKey</i> to continue the scan in a subsequent operation. The results also include the number of items exceeding the limit. A scan can result in no table data meeting the filter criteria. </p> <p>The result set is eventually consistent. </p> <p>By default, <i>Scan</i> operations proceed sequentially; however, for faster performance on large tables, applications can request a parallel <i>Scan</i> by specifying the <i>Segment</i> and <i>TotalSegments</i> parameters. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html#QueryAndScanParallelScan\">Parallel Scan</a> in the Amazon DynamoDB Developer Guide.</p>"
-    },
-    "UpdateItem":{
-      "name":"UpdateItem",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"UpdateItemInput",
-        "documentation":"<p>Represents the input of an <i>UpdateItem</i> operation.</p>"
-      },
-      "output":{
-        "shape":"UpdateItemOutput",
-        "documentation":"<p>Represents the output of an <i>UpdateItem</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ConditionalCheckFailedException",
-          "exception":true,
-          "documentation":"<p>A condition specified in the operation could not be evaluated.</p>"
-        },
-        {
-          "shape":"ProvisionedThroughputExceededException",
-          "exception":true,
-          "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"ItemCollectionSizeLimitExceededException",
-          "exception":true,
-          "documentation":"<p>An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p> Edits an existing item's attributes, or inserts a new item if it does not already exist. You can put, delete, or add attribute values. You can also perform a conditional update (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).</p> <p>In addition to updating an item, you can also return the item's attribute values in the same operation, using the <i>ReturnValues</i> parameter.</p>"
-    },
-    "UpdateTable":{
-      "name":"UpdateTable",
-      "http":{
-        "method":"POST",
-        "requestUri":"/"
-      },
-      "input":{
-        "shape":"UpdateTableInput",
-        "documentation":"<p>Represents the input of an <i>UpdateTable</i> operation.</p>"
-      },
-      "output":{
-        "shape":"UpdateTableOutput",
-        "documentation":"<p>Represents the output of an <i>UpdateTable</i> operation.</p>"
-      },
-      "errors":[
-        {
-          "shape":"ResourceInUseException",
-          "exception":true,
-          "documentation":"<p>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 <code>CREATING</code> state.</p>"
-        },
-        {
-          "shape":"ResourceNotFoundException",
-          "exception":true,
-          "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-        },
-        {
-          "shape":"LimitExceededException",
-          "exception":true,
-          "documentation":"<p>The number of concurrent table requests (cumulative number of tables in the <code>CREATING</code>, <code>DELETING</code> or <code>UPDATING</code> state) exceeds the maximum allowed of 10.</p> <p>Also, for tables with secondary indexes, only one of those tables can be in the <code>CREATING</code> state at any point in time. Do not attempt to create more than one such table simultaneously.</p> <p>The total limit of tables in the <code>ACTIVE</code> state is 250.</p>"
-        },
-        {
-          "shape":"InternalServerError",
-          "exception":true,
-          "fault":true,
-          "documentation":"<p>An error occurred on the server side.</p>"
-        }
-      ],
-      "documentation":"<p>Updates the provisioned throughput for the given table. Setting the throughput for a table helps you manage performance and is part of the provisioned throughput feature of DynamoDB.</p> <p>The provisioned throughput values can be upgraded or downgraded based on the maximums and minimums listed in the <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html\">Limits</a> section in the Amazon DynamoDB Developer Guide.</p> <p>The table must be in the <code>ACTIVE</code> state for this operation to succeed. <i>UpdateTable</i> is an asynchronous operation; while executing the operation, the table is in the <code>UPDATING</code> state. While the table is in the <code>UPDATING</code> state, the table still has the provisioned throughput from before the call. The new provisioned throughput setting is in effect only when the table returns to the <code>ACTIVE</code> state after the <i>UpdateTable</i> operation. </p> <p>You cannot add, modify or delete indexes using <i>UpdateTable</i>. Indexes can only be defined at table creation time.</p>"
-    }
-  },
-  "shapes":{
-    "AttributeAction":{
-      "type":"string",
-      "enum":[
-        "ADD",
-        "PUT",
-        "DELETE"
-      ]
-    },
-    "AttributeDefinition":{
-      "type":"structure",
-      "required":[
-        "AttributeName",
-        "AttributeType"
-      ],
-      "members":{
-        "AttributeName":{
-          "shape":"KeySchemaAttributeName",
-          "documentation":"<p>A name for the attribute.</p>"
-        },
-        "AttributeType":{
-          "shape":"ScalarAttributeType",
-          "documentation":"<p>The data type for the attribute.</p>"
-        }
-      },
-      "documentation":"<p>Represents an attribute for describing the key schema for the table and indexes.</p>"
-    },
-    "AttributeDefinitions":{
-      "type":"list",
-      "member":{"shape":"AttributeDefinition"}
-    },
-    "AttributeMap":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"AttributeValue"}
-    },
-    "AttributeName":{
-      "type":"string",
-      "max":65535
-    },
-    "AttributeNameList":{
-      "type":"list",
-      "member":{"shape":"AttributeName"},
-      "min":1
-    },
-    "AttributeUpdates":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"AttributeValueUpdate"}
-    },
-    "AttributeValue":{
-      "type":"structure",
-      "members":{
-        "S":{
-          "shape":"StringAttributeValue",
-          "documentation":"<p>A String data type</p>"
-        },
-        "N":{
-          "shape":"NumberAttributeValue",
-          "documentation":"<p>A Number data type</p>"
-        },
-        "B":{
-          "shape":"BinaryAttributeValue",
-          "documentation":"<p>A Binary data type</p>"
-        },
-        "SS":{
-          "shape":"StringSetAttributeValue",
-          "documentation":"<p>A String set data type</p>"
-        },
-        "NS":{
-          "shape":"NumberSetAttributeValue",
-          "documentation":"<p> Number set data type</p>"
-        },
-        "BS":{
-          "shape":"BinarySetAttributeValue",
-          "documentation":"<p>A Binary set data type</p>"
-        }
-      },
-      "documentation":"<p>Represents the data for an attribute. You can set one, and only one, of the elements.</p>"
-    },
-    "AttributeValueList":{
-      "type":"list",
-      "member":{"shape":"AttributeValue"}
-    },
-    "AttributeValueUpdate":{
-      "type":"structure",
-      "members":{
-        "Value":{"shape":"AttributeValue"},
-        "Action":{
-          "shape":"AttributeAction",
-          "documentation":"<p>Specifies how to perform the update. Valid values are <code>PUT</code>, <code>DELETE</code>, and <code>ADD</code>. The behavior depends on whether the specified primary key already exists in the table.</p> <p> <b>If an item with the specified <i>Key</i> is found in the table:</b> </p> <ul> <li> <p><code>PUT</code> - Adds the specified attribute to the item. If the attribute already exists, it is replaced by the new value. </p> </li> <li> <p><code>DELETE</code> - If no value is specified, the attribute and its value are removed from the item. The data type of the specified value must match the existing value's data type.</p> <p>If a <i>set</i> of values is specified, then those values are subtracted from the old set. For example, if the attribute value was the set <code>[a,b,c]</code> and the <i>DELETE</i> action specified <code>[a,c]</code>, then the final attribute value would be <code>[b]</code>. Specifying an empty set is an error.</p> </li> <li> <p><code>ADD</code> - If the attribute does not already exist, then the attribute and its values are added to the item. If the attribute does exist, then the behavior of <code>ADD</code> depends on the data type of the attribute:</p> <ul> <li> <p>If the existing attribute is a number, and if <i>Value</i> is also a number, then the <i>Value</i> is mathematically added to the existing attribute. If <i>Value</i> is a negative number, then it is subtracted from the existing attribute.</p> </li> <li> <p>If the existing data type is a set, and if the <i>Value</i> is also a set, then the <i>Value</i> is added to the existing set. (This is a <i>set</i> operation, not mathematical addition.) For example, if the attribute value was the set <code>[1,2]</code>, and the <code>ADD</code> action specified <code>[3]</code>, then the final attribute value would be <code>[1,2,3]</code>. An error occurs if an Add action is specified for a set attribute and the attribute type specified does not match the existing set type. </p> <p>Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the <i>Value</i> must also be a set of strings. The same holds true for number sets and binary sets.</p> </li> </ul> <p>This action is only valid for an existing attribute whose data type is number or is a set. Do not use <code>ADD</code> for any other data types.</p> </li> </ul> <p> <b>If no item with the specified <i>Key</i> is found:</b> </p> <ul> <li> <p><code>PUT</code> - DynamoDB creates a new item with the specified primary key, and then adds the attribute. </p> </li> <li> <p><code>DELETE</code> - Nothing happens; there is no attribute to delete.</p> </li> <li> <p><code>ADD</code> - DynamoDB creates an item with the supplied primary key and number (or set of numbers) for the attribute value. The only data types allowed are number and number set; no other data types can be specified.</p> </li> </ul>"
-        }
-      },
-      "documentation":"<p>For the <i>UpdateItem</i> operation, represents the attributes to be modified, the action to perform on each, and the new value for each.</p> <p>Attribute values cannot be null; string and binary type attributes must have lengths greater than zero; and set type attributes must not be empty. Requests with empty values will be rejected with a <i>ValidationException</i>.</p>"
-    },
-    "BatchGetItemInput":{
-      "type":"structure",
-      "required":["RequestItems"],
-      "members":{
-        "RequestItems":{
-          "shape":"BatchGetRequestMap",
-          "documentation":"<p>A map of one or more table names and, for each table, the corresponding primary keys for the items to retrieve. Each table name can be invoked only once.</p> <p>Each element in the map consists of the following:</p> <ul> <li> <p><i>Keys</i> - An array of primary key attribute values that define specific items in the table. For each primary key, you must provide <i>all</i> of the key attributes. For example, with a hash type primary key, you only need to specify the hash attribute. For a hash-and-range type primary key, you must specify <i>both</i> the hash attribute and the range attribute.</p> </li> <li> <p><i>AttributesToGet</i> - One or more attributes to be retrieved from the table. By default, all attributes are returned. If a specified attribute is not found, it does not appear in the result.</p> <p>Note that <i>AttributesToGet</i> has no effect on provisioned throughput consumption. DynamoDB determines capacity units consumed based on item size, not on the amount of data that is returned to an application.</p> </li> <li> <p><i>ConsistentRead</i> - If <code>true</code>, a strongly consistent read is used; if <code>false</code> (the default), an eventually consistent read is used.</p> </li> </ul>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"}
-      },
-      "documentation":"<p>Represents the input of a <i>BatchGetItem</i> operation.</p>"
-    },
-    "BatchGetItemOutput":{
-      "type":"structure",
-      "members":{
-        "Responses":{
-          "shape":"BatchGetResponseMap",
-          "documentation":"<p>A map of table name to a list of items. Each object in <i>Responses</i> consists of a table name, along with a map of attribute data consisting of the data type and attribute value.</p>"
-        },
-        "UnprocessedKeys":{
-          "shape":"BatchGetRequestMap",
-          "documentation":"<p>A map of tables and their respective keys that were not processed with the current response. The <i>UnprocessedKeys</i> value is in the same form as <i>RequestItems</i>, so the value can be provided directly to a subsequent <i>BatchGetItem</i> operation. For more information, see <i>RequestItems</i> in the Request Parameters section.</p> <p>Each element consists of:</p> <ul> <li> <p><i>Keys</i> - An array of primary key attribute values that define specific items in the table.</p> </li> <li> <p><i>AttributesToGet</i> - One or more attributes to be retrieved from the table or index. By default, all attributes are returned. If a specified attribute is not found, it does not appear in the result.</p> </li> <li> <p><i>ConsistentRead</i> - The consistency of a read operation. If set to <code>true</code>, then a strongly consistent read is used; otherwise, an eventually consistent read is used.</p> </li> </ul> <p>If there are no unprocessed keys remaining, the response contains an empty <i>UnprocessedKeys</i> map.</p>"
-        },
-        "ConsumedCapacity":{
-          "shape":"ConsumedCapacityMultiple",
-          "documentation":"<p>The write capacity units consumed by the operation.</p> <p>Each element consists of:</p> <ul> <li> <p><i>TableName</i> - The table that consumed the provisioned throughput.</p> </li> <li> <p><i>CapacityUnits</i> - The total number of capacity units consumed.</p> </li> </ul>"
-        }
-      },
-      "documentation":"<p>Represents the output of a <i>BatchGetItem</i> operation.</p>"
-    },
-    "BatchGetRequestMap":{
-      "type":"map",
-      "key":{"shape":"TableName"},
-      "value":{"shape":"KeysAndAttributes"},
-      "min":1,
-      "max":100
-    },
-    "BatchGetResponseMap":{
-      "type":"map",
-      "key":{"shape":"TableName"},
-      "value":{"shape":"ItemList"}
-    },
-    "BatchWriteItemInput":{
-      "type":"structure",
-      "required":["RequestItems"],
-      "members":{
-        "RequestItems":{
-          "shape":"BatchWriteItemRequestMap",
-          "documentation":"<p>A map of one or more table names and, for each table, a list of operations to be performed (<i>DeleteRequest</i> or <i>PutRequest</i>). Each element in the map consists of the following:</p> <ul> <li> <p><i>DeleteRequest</i> - Perform a <i>DeleteItem</i> operation on the specified item. The item to be deleted is identified by a <i>Key</i> subelement:</p> <ul> <li> <p><i>Key</i> - 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 <i>all</i> of the key attributes. For example, with a hash type primary key, you only need to specify the hash attribute. For a hash-and-range type primary key, you must specify <i>both</i> the hash attribute and the range attribute.</p> </li> </ul> </li> <li> <p><i>PutRequest</i> - Perform a <i>PutItem</i> operation on the specified item. The item to be put is identified by an <i>Item</i> subelement:</p> <ul> <li> <p><i>Item</i> - 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 will be rejected with a <i>ValidationException</i>.</p> <p>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.</p> </li> </ul> </li> </ul>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"},
-        "ReturnItemCollectionMetrics":{
-          "shape":"ReturnItemCollectionMetrics",
-          "documentation":"<p>If set to <code>SIZE</code>, statistics about item collections, if any, that were modified during the operation are returned in the response. If set to <code>NONE</code> (the default), no statistics are returned.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of a <i>BatchWriteItem</i> operation.</p>"
-    },
-    "BatchWriteItemOutput":{
-      "type":"structure",
-      "members":{
-        "UnprocessedItems":{
-          "shape":"BatchWriteItemRequestMap",
-          "documentation":"<p>A map of tables and requests against those tables that were not processed. The <i>UnprocessedItems</i> value is in the same form as <i>RequestItems</i>, so you can provide this value directly to a subsequent <i>BatchGetItem</i> operation. For more information, see <i>RequestItems</i> in the Request Parameters section.</p> <p>Each <i>UnprocessedItems</i> entry consists of a table name and, for that table, a list of operations to perform (<i>DeleteRequest</i> or <i>PutRequest</i>).</p> <ul> <li> <p><i>DeleteRequest</i> - Perform a <i>DeleteItem</i> operation on the specified item. The item to be deleted is identified by a <i>Key</i> subelement:</p> <ul> <li> <p><i>Key</i> - 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.</p> </li> </ul> </li> <li> <p><i>PutRequest</i> - Perform a <i>PutItem</i> operation on the specified item. The item to be put is identified by an <i>Item</i> subelement:</p> <ul> <li> <p><i>Item</i> - 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 will be rejected with a <i>ValidationException</i>.</p> <p>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.</p> </li> </ul> </li> </ul> <p>If there are no unprocessed items remaining, the response contains an empty <i>UnprocessedItems</i> map.</p>"
-        },
-        "ItemCollectionMetrics":{
-          "shape":"ItemCollectionMetricsPerTable",
-          "documentation":"<p>A list of tables that were processed by <i>BatchWriteItem</i> and, for each table, information about any item collections that were affected by individual <i>DeleteItem</i> or <i>PutItem</i> operations.</p> <p>Each entry consists of the following subelements:</p> <ul> <li> <p><i>ItemCollectionKey</i> - The hash key value of the item collection. This is the same as the hash key of the item.</p> </li> <li> <p><i>SizeEstimateRange</i> - An estimate of item collection size, expressed in GB. This is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on the table. Use this estimate to measure whether a local secondary index is approaching its size limit.</p> <p>The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.</p> </li> </ul>"
-        },
-        "ConsumedCapacity":{
-          "shape":"ConsumedCapacityMultiple",
-          "documentation":"<p>The capacity units consumed by the operation.</p> <p>Each element consists of:</p> <ul> <li> <p><i>TableName</i> - The table that consumed the provisioned throughput.</p> </li> <li> <p><i>CapacityUnits</i> - The total number of capacity units consumed.</p> </li> </ul>"
-        }
-      },
-      "documentation":"<p>Represents the output of a <i>BatchWriteItem</i> operation.</p>"
-    },
-    "BatchWriteItemRequestMap":{
-      "type":"map",
-      "key":{"shape":"TableName"},
-      "value":{"shape":"WriteRequests"},
-      "min":1,
-      "max":25
-    },
-    "BinaryAttributeValue":{"type":"blob"},
-    "BinarySetAttributeValue":{
-      "type":"list",
-      "member":{"shape":"BinaryAttributeValue"}
-    },
-    "BooleanObject":{"type":"boolean"},
-    "Capacity":{
-      "type":"structure",
-      "members":{
-        "CapacityUnits":{
-          "shape":"ConsumedCapacityUnits",
-          "documentation":"<p>The total number of capacity units consumed on a table or an index.</p>"
-        }
-      },
-      "documentation":"<p>Represents the amount of provisioned throughput capacity consumed on a table or an index. </p>"
-    },
-    "ComparisonOperator":{
-      "type":"string",
-      "enum":[
-        "EQ",
-        "NE",
-        "IN",
-        "LE",
-        "LT",
-        "GE",
-        "GT",
-        "BETWEEN",
-        "NOT_NULL",
-        "NULL",
-        "CONTAINS",
-        "NOT_CONTAINS",
-        "BEGINS_WITH"
-      ]
-    },
-    "Condition":{
-      "type":"structure",
-      "required":["ComparisonOperator"],
-      "members":{
-        "AttributeValueList":{
-          "shape":"AttributeValueList",
-          "documentation":"<p>One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\">http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p>"
-        },
-        "ComparisonOperator":{
-          "shape":"ComparisonOperator",
-          "documentation":"<p>A comparator for evaluating attributes. For example, equals, greater than, less than, etc.</p> <p>The following comparison operators are available:</p> <p><code>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</code></p> <p>The following are descriptions of each comparison operator.</p> <ul> <li> <p><code>EQ</code> : Equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NE</code> : Not equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LE</code> : Less than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LT</code> : Less than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GE</code> : Greater than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GT</code> : Greater than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NOT_NULL</code> : The attribute exists. </p> </li> <li> <p><code>NULL</code> : The attribute does not exist. </p> </li> <li> <p><code>CONTAINS</code> : checks for a subsequence, or value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for a substring match. If the target attribute of the comparison is Binary, then the operation looks for a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for a member of the set (not as a substring).</p> </li> <li> <p><code>NOT_CONTAINS</code> : checks for absence of a subsequence, or absence of a value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for the absence of a substring match. If the target attribute of the comparison is Binary, then the operation checks for the absence of a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for the absence of a member of the set (not as a substring).</p></li> <li> <p><code>BEGINS_WITH</code> : checks for a prefix. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String or Binary (not a Number or a set). The target attribute of the comparison must be a String or Binary (not a Number or a set).</p> <p/> </li> <li> <p><code>IN</code> : checks for exact matches.</p> <p><i>AttributeValueList</i> can contain more than one <i>AttributeValue</i> of type String, Number, or Binary (not a set). The target attribute of the comparison must be of the same type and exact value to match. A String never matches a String set.</p> </li> <li> <p><code>BETWEEN</code> : Greater than or equal to the first value, and less than or equal to the second value. </p> <p><i>AttributeValueList</i> must contain two <i>AttributeValue</i> elements of the same type, either String, Number, or Binary (not a set). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not compare to <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code></p> </li> </ul> <p>For usage examples of <i>AttributeValueList</i> and <i>ComparisonOperator</i>, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html#ConditionalExpressions\">Conditional Expressions</a> in the Amazon DynamoDB Developer Guide.</p>"
-        }
-      },
-      "documentation":"<p>Represents the selection criteria for a <i>Query</i> or <i>Scan</i> operation:</p> <ul> <li> <p>For a <i>Query</i> operation, <i>Condition</i> is used for specifying the <i>KeyConditions</i> to use when querying a table or an index. For <i>KeyConditions</i>, only the following comparison operators are supported:</p> <p> <code>EQ | LE | LT | GE | GT | BEGINS_WITH | BETWEEN</code> </p> <p><i>Condition</i> is also used in a <i>QueryFilter</i>, which evaluates the query results and returns only the desired values.</p> </li> <li> <p>For a <i>Scan</i> operation, <i>Condition</i> is used in a <i>ScanFilter</i>, which evaluates the scan results and returns only the desired values.</p> </li> </ul>"
-    },
-    "ConditionalCheckFailedException":{
-      "type":"structure",
-      "members":{
-        "message":{
-          "shape":"ErrorMessage",
-          "documentation":"<p>The conditional request failed.</p>"
-        }
-      },
-      "exception":true,
-      "documentation":"<p>A condition specified in the operation could not be evaluated.</p>"
-    },
-    "ConditionalOperator":{
-      "type":"string",
-      "enum":[
-        "AND",
-        "OR"
-      ]
-    },
-    "ConsistentRead":{"type":"boolean"},
-    "ConsumedCapacity":{
-      "type":"structure",
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table that was affected by the operation.</p>"
-        },
-        "CapacityUnits":{
-          "shape":"ConsumedCapacityUnits",
-          "documentation":"<p>The total number of capacity units consumed by the operation.</p>"
-        },
-        "Table":{
-          "shape":"Capacity",
-          "documentation":"<p>The amount of throughput consumed on the table affected by the operation.</p>"
-        },
-        "LocalSecondaryIndexes":{
-          "shape":"SecondaryIndexesCapacityMap",
-          "documentation":"<p>The amount of throughput consumed on each local index affected by the operation.</p>"
-        },
-        "GlobalSecondaryIndexes":{
-          "shape":"SecondaryIndexesCapacityMap",
-          "documentation":"<p>The amount of throughput consumed on each global index affected by the operation.</p>"
-        }
-      },
-      "documentation":"<p>Represents the capacity units consumed by an operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation. <i>ConsumedCapacity</i> is only returned if it was asked for in the request. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ProvisionedThroughputIntro.html\">Provisioned Throughput</a> in the Amazon DynamoDB Developer Guide.</p>"
-    },
-    "ConsumedCapacityMultiple":{
-      "type":"list",
-      "member":{"shape":"ConsumedCapacity"}
-    },
-    "ConsumedCapacityUnits":{"type":"double"},
-    "CreateTableInput":{
-      "type":"structure",
-      "required":[
-        "AttributeDefinitions",
-        "TableName",
-        "KeySchema",
-        "ProvisionedThroughput"
-      ],
-      "members":{
-        "AttributeDefinitions":{
-          "shape":"AttributeDefinitions",
-          "documentation":"<p>An array of attributes that describe the key schema for the table and indexes.</p>"
-        },
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table to create.</p>"
-        },
-        "KeySchema":{
-          "shape":"KeySchema",
-          "documentation":"<p>Specifies the attributes that make up the primary key for a table or an index. The attributes in <i>KeySchema</i> must also be defined in the <i>AttributeDefinitions</i> array. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataModel.html\">Data Model</a> in the Amazon DynamoDB Developer Guide.</p> <p>Each <i>KeySchemaElement</i> in the array is composed of:</p> <ul> <li> <p><i>AttributeName</i> - The name of this key attribute.</p> </li> <li> <p><i>KeyType</i> - Determines whether the key attribute is <code>HASH</code> or <code>RANGE</code>.</p> </li> </ul> <p>For a primary key that consists of a hash attribute, you must specify exactly one element with a <i>KeyType</i> of <code>HASH</code>.</p> <p>For a primary key that consists of hash and range attributes, you must specify exactly two elements, in this order: The first element must have a <i>KeyType</i> of <code>HASH</code>, and the second element must have a <i>KeyType</i> of <code>RANGE</code>.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#WorkingWithTables.primary.key\">Specifying the Primary Key</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "LocalSecondaryIndexes":{
-          "shape":"LocalSecondaryIndexList",
-          "documentation":"<p>One or more local secondary indexes (the maximum is five) to be created on the table. Each index is scoped to a given hash key value. There is a 10 GB size limit per hash key; otherwise, the size of a local secondary index is unconstrained.</p> <p>Each local secondary index in the array includes the following:</p> <ul> <li> <p><i>IndexName</i> - The name of the local secondary index. Must be unique only for this table.</p> <p></p> </li> <li> <p><i>KeySchema</i> - Specifies the key schema for the local secondary index. The key schema must begin with the same hash key attribute as the table.</p> </li> <li> <p><i>Projection</i> - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of:</p> <ul> <li> <p><i>ProjectionType</i> - One of the following:</p> <ul> <li> <p><code>KEYS_ONLY</code> - Only the index and primary keys are projected into the index.</p> </li> <li> <p><code>INCLUDE</code> - Only the specified table attributes are projected into the index. The list of projected attributes are in <i>NonKeyAttributes</i>.</p> </li> <li> <p><code>ALL</code> - All of the table attributes are projected into the index.</p> </li> </ul> </li> <li> <p><i>NonKeyAttributes</i> - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes specified in <i>NonKeyAttributes</i>, summed across all of the secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total.</p> </li> </ul> </li> </ul>"
-        },
-        "GlobalSecondaryIndexes":{
-          "shape":"GlobalSecondaryIndexList",
-          "documentation":"<p>One or more global secondary indexes (the maximum is five) to be created on the table. Each global secondary index in the array includes the following:</p> <ul> <li> <p><i>IndexName</i> - The name of the global secondary index. Must be unique only for this table.</p> <p></p> </li> <li> <p><i>KeySchema</i> - Specifies the key schema for the global secondary index.</p> </li> <li> <p><i>Projection</i> - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of:</p> <ul> <li> <p><i>ProjectionType</i> - One of the following:</p> <ul> <li> <p><code>KEYS_ONLY</code> - Only the index and primary keys are projected into the index.</p> </li> <li> <p><code>INCLUDE</code> - Only the specified table attributes are projected into the index. The list of projected attributes are in <i>NonKeyAttributes</i>.</p> </li> <li> <p><code>ALL</code> - All of the table attributes are projected into the index.</p> </li> </ul> </li> <li> <p><i>NonKeyAttributes</i> - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes specified in <i>NonKeyAttributes</i>, summed across all of the secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total.</p> </li> </ul> </li> <li> <p><i>ProvisionedThroughput</i> - The provisioned throughput settings for the global secondary index, consisting of read and write capacity units.</p> </li> </ul>"
-        },
-        "ProvisionedThroughput":{"shape":"ProvisionedThroughput"}
-      },
-      "documentation":"<p>Represents the input of a <i>CreateTable</i> operation.</p>"
-    },
-    "CreateTableOutput":{
-      "type":"structure",
-      "members":{
-        "TableDescription":{"shape":"TableDescription"}
-      },
-      "documentation":"<p>Represents the output of a <i>CreateTable</i> operation.</p>"
-    },
-    "Date":{"type":"timestamp"},
-    "DeleteItemInput":{
-      "type":"structure",
-      "required":[
-        "TableName",
-        "Key"
-      ],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table from which to delete the item.</p>"
-        },
-        "Key":{
-          "shape":"Key",
-          "documentation":"<p>A map of attribute names to <i>AttributeValue</i> objects, representing the primary key of the item to delete.</p> <p>For the primary key, you must provide <i>all</i> of the attributes. For example, with a hash type primary key, you only need to specify the hash attribute. For a hash-and-range type primary key, you must specify <i>both</i> the hash attribute and the range attribute.</p>"
-        },
-        "Expected":{
-          "shape":"ExpectedAttributeMap",
-          "documentation":"<p>A map of attribute/condition pairs. This is the conditional block for the <i>DeleteItem</i> operation.</p> <p>Each element of <i>Expected</i> consists of an attribute name, a comparison operator, and one or more values. DynamoDB compares the attribute with the value(s) you supplied, using the comparison operator. For each <i>Expected</i> element, the result of the evaluation is either true or false.</p> <p>If you specify more than one element in the <i>Expected</i> map, then by default all of the conditions must evaluate to true. In other words, the conditions are ANDed together. (You can use the <i>ConditionalOperator</i> parameter to OR the conditions instead. If you do this, then at least one of the conditions must evaluate to true, rather than all of them.)</p> <p>If the <i>Expected</i> map evaluates to true, then the conditional operation succeeds; otherwise, it fails.</p> <p>Each item in <i>Expected</i> represents an attribute name for DynamoDB to check, along with an <i>AttributeValueList</i> and a <i>ComparisonOperator</i>:</p> <ul> <li> <p><i>AttributeValueList</i> - One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\" >http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p> </li> <li> <p><i>ComparisonOperator</i> - A comparator for evaluating attributes in the <i>AttributeValueList</i>. When performing the comparison, DynamoDB uses strongly consistent reads.</p> <p>The following comparison operators are available:</p> <p><code>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</code></p> <p>The following are descriptions of each comparison operator.</p> <ul> <li> <p><code>EQ</code> : Equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NE</code> : Not equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LE</code> : Less than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LT</code> : Less than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GE</code> : Greater than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GT</code> : Greater than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NOT_NULL</code> : The attribute exists. </p> </li> <li> <p><code>NULL</code> : The attribute does not exist. </p> </li> <li> <p><code>CONTAINS</code> : checks for a subsequence, or value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for a substring match. If the target attribute of the comparison is Binary, then the operation looks for a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for a member of the set (not as a substring).</p> </li> <li> <p><code>NOT_CONTAINS</code> : checks for absence of a subsequence, or absence of a value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for the absence of a substring match. If the target attribute of the comparison is Binary, then the operation checks for the absence of a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for the absence of a member of the set (not as a substring).</p></li> <li> <p><code>BEGINS_WITH</code> : checks for a prefix. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String or Binary (not a Number or a set). The target attribute of the comparison must be a String or Binary (not a Number or a set).</p> <p/> </li> <li> <p><code>IN</code> : checks for exact matches.</p> <p><i>AttributeValueList</i> can contain more than one <i>AttributeValue</i> of type String, Number, or Binary (not a set). The target attribute of the comparison must be of the same type and exact value to match. A String never matches a String set.</p> </li> <li> <p><code>BETWEEN</code> : Greater than or equal to the first value, and less than or equal to the second value. </p> <p><i>AttributeValueList</i> must contain two <i>AttributeValue</i> elements of the same type, either String, Number, or Binary (not a set). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not compare to <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code></p> </li> </ul> </li> </ul> <p>For usage examples of <i>AttributeValueList</i> and <i>ComparisonOperator</i>, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html#ConditionalExpressions\" >Conditional Expressions</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "ConditionalOperator":{
-          "shape":"ConditionalOperator",
-          "documentation":"<p>A logical operator to apply to the conditions in the <i>Expected</i> map:</p> <ul> <li><p><code>AND</code> - If <i>all</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> <li><p><code>OR</code> - If <i>at least one</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> </ul> <p>If you omit <i>ConditionalOperator</i>, then <code>AND</code> is the default.</p> <p>The operation will succeed only if the entire map evaluates to true.</p>"
-        },
-        "ReturnValues":{
-          "shape":"ReturnValue",
-          "documentation":"<p>Use <i>ReturnValues</i> if you want to get the item attributes as they appeared before they were deleted. For <i>DeleteItem</i>, the valid values are:</p> <ul> <li> <p><code>NONE</code> - If <i>ReturnValues</i> is not specified, or if its value is <code>NONE</code>, then nothing is returned. (This is the default for <i>ReturnValues</i>.)</p> </li> <li> <p><code>ALL_OLD</code> - The content of the old item is returned.</p> </li> </ul>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"},
-        "ReturnItemCollectionMetrics":{
-          "shape":"ReturnItemCollectionMetrics",
-          "documentation":"<p>If set to <code>SIZE</code>, statistics about item collections, if any, that were modified during the operation are returned in the response. If set to <code>NONE</code> (the default), no statistics are returned.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of a <i>DeleteItem</i> operation.</p>"
-    },
-    "DeleteItemOutput":{
-      "type":"structure",
-      "members":{
-        "Attributes":{
-          "shape":"AttributeMap",
-          "documentation":"<p>A map of attribute names to <i>AttributeValue</i> objects, representing the item as it appeared before the <i>DeleteItem</i> operation. This map appears in the response only if <i>ReturnValues</i> was specified as <code>ALL_OLD</code> in the request.</p>"
-        },
-        "ConsumedCapacity":{"shape":"ConsumedCapacity"},
-        "ItemCollectionMetrics":{
-          "shape":"ItemCollectionMetrics",
-          "documentation":"<p>Information about item collections, if any, that were affected by the operation. <i>ItemCollectionMetrics</i> is only returned if it was asked for in the request. If the table does not have any local secondary indexes, this information is not returned in the response.</p> <p>Each <i>ItemCollectionMetrics</i> element consists of:</p> <ul> <li><p><i>ItemCollectionKey</i> - The hash key value of the item collection. This is the same as the hash key of the item.</p></li> <li><p><i>SizeEstimateRange</i> - An estimate of item collection size, measured in gigabytes. This is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on that table. Use this estimate to measure whether a local secondary index is approaching its size limit.</p> <p>The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.</p> </li> </ul>"
-        }
-      },
-      "documentation":"<p>Represents the output of a <i>DeleteItem</i> operation.</p>"
-    },
-    "DeleteRequest":{
-      "type":"structure",
-      "required":["Key"],
-      "members":{
-        "Key":{
-          "shape":"Key",
-          "documentation":"<p>A map of attribute name to attribute values, representing the primary key of the item to delete. All of the table's primary key attributes must be specified, and their data types must match those of the table's key schema.</p>"
-        }
-      },
-      "documentation":"<p>Represents a request to perform a <i>DeleteItem</i> operation on an item.</p>"
-    },
-    "DeleteTableInput":{
-      "type":"structure",
-      "required":["TableName"],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p> The name of the table to delete.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of a <i>DeleteTable</i> operation.</p>"
-    },
-    "DeleteTableOutput":{
-      "type":"structure",
-      "members":{
-        "TableDescription":{"shape":"TableDescription"}
-      },
-      "documentation":"<p>Represents the output of a <i>DeleteTable</i> operation.</p>"
-    },
-    "DescribeTableInput":{
-      "type":"structure",
-      "required":["TableName"],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p> The name of the table to describe.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of a <i>DescribeTable</i> operation.</p>"
-    },
-    "DescribeTableOutput":{
-      "type":"structure",
-      "members":{
-        "Table":{"shape":"TableDescription"}
-      },
-      "documentation":"<p>Represents the output of a <i>DescribeTable</i> operation.</p>"
-    },
-    "ErrorMessage":{"type":"string"},
-    "ExpectedAttributeMap":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"ExpectedAttributeValue"}
-    },
-    "ExpectedAttributeValue":{
-      "type":"structure",
-      "members":{
-        "Value":{"shape":"AttributeValue"},
-        "Exists":{
-          "shape":"BooleanObject",
-          "documentation":"<p>Causes DynamoDB to evaluate the value before attempting a conditional operation:</p> <ul> <li> <p>If <i>Exists</i> is <code>true</code>, DynamoDB will check to see if that attribute value already exists in the table. If it is found, then the operation succeeds. If it is not found, the operation fails with a <i>ConditionalCheckFailedException</i>.</p> </li> <li> <p>If <i>Exists</i> is <code>false</code>, DynamoDB assumes that the attribute value does <i>not</i> exist in the table. If in fact the value does not exist, then the assumption is valid and the operation succeeds. If the value is found, despite the assumption that it does not exist, the operation fails with a <i>ConditionalCheckFailedException</i>.</p> </li> </ul> <p>The default setting for <i>Exists</i> is <code>true</code>. If you supply a <i>Value</i> all by itself, DynamoDB assumes the attribute exists: You don't have to set <i>Exists</i> to <code>true</code>, because it is implied.</p> <p>DynamoDB returns a <i>ValidationException</i> if:</p> <ul> <li> <p><i>Exists</i> is <code>true</code> but there is no <i>Value</i> to check. (You expect a value to exist, but don't specify what that value is.)</p> </li> <li> <p><i>Exists</i> is <code>false</code> but you also specify a <i>Value</i>. (You cannot expect an attribute to have a value, while also expecting it not to exist.)</p> </li> </ul>"
-        },
-        "ComparisonOperator":{
-          "shape":"ComparisonOperator",
-          "documentation":"<p>A comparator for evaluating attributes in the <i>AttributeValueList</i>. For example, equals, greater than, less than, etc.</p> <p>The following comparison operators are available:</p> <p><code>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</code></p> <p>The following are descriptions of each comparison operator.</p> <ul> <li> <p><code>EQ</code> : Equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NE</code> : Not equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LE</code> : Less than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LT</code> : Less than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GE</code> : Greater than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GT</code> : Greater than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NOT_NULL</code> : The attribute exists. </p> </li> <li> <p><code>NULL</code> : The attribute does not exist. </p> </li> <li> <p><code>CONTAINS</code> : checks for a subsequence, or value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for a substring match. If the target attribute of the comparison is Binary, then the operation looks for a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for a member of the set (not as a substring).</p> </li> <li> <p><code>NOT_CONTAINS</code> : checks for absence of a subsequence, or absence of a value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for the absence of a substring match. If the target attribute of the comparison is Binary, then the operation checks for the absence of a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for the absence of a member of the set (not as a substring).</p></li> <li> <p><code>BEGINS_WITH</code> : checks for a prefix. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String or Binary (not a Number or a set). The target attribute of the comparison must be a String or Binary (not a Number or a set).</p> <p/> </li> <li> <p><code>IN</code> : checks for exact matches.</p> <p><i>AttributeValueList</i> can contain more than one <i>AttributeValue</i> of type String, Number, or Binary (not a set). The target attribute of the comparison must be of the same type and exact value to match. A String never matches a String set.</p> </li> <li> <p><code>BETWEEN</code> : Greater than or equal to the first value, and less than or equal to the second value. </p> <p><i>AttributeValueList</i> must contain two <i>AttributeValue</i> elements of the same type, either String, Number, or Binary (not a set). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not compare to <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code></p> </li> </ul>"
-        },
-        "AttributeValueList":{
-          "shape":"AttributeValueList",
-          "documentation":"<p>One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\">http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p> <p>For information on specifying data types in JSON, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataFormat.html\">JSON Data Format</a> in the Amazon DynamoDB Developer Guide.</p>"
-        }
-      },
-      "documentation":"<p>Represents a condition to be compared with an attribute value. This condition can be used with <i>DeleteItem</i>, <i>PutItem</i> or <i>UpdateItem</i> operations; if the comparison evaluates to true, the operation succeeds; if not the operation fails. You can use <i>ExpectedAttributeValue</i> in one of two different ways:</p> <ul> <li> <p>Use <i>AttributeValueList</i> to specify one or more values to compare against an attribute. Use <i>ComparisonOperator</i> to specify how you want to perform the comparison. If the comparison evaluates to true, then the conditional operation succeeds.</p> </li> <li> <p>Use <i>Value</i> to specify a value that DynamoDB will compare against an attribute. If the values match, then <i>ExpectedAttributeValue</i> evaluates to true and the conditional operation succeeds. Optionally, you can also set <i>Exists</i> to false, indicating that you <i>do not</i> expect to find the attribute value in the table. In this case, the conditional operation succeeds only if the comparison evaluates to false.</p> </li> </ul> <p><i>Value</i> and <i>Exists</i> are incompatible with <i>AttributeValueList</i> and <i>ComparisonOperator</i>. If you attempt to use both sets of parameters at once, DynamoDB will throw a <i>ValidationException</i>.</p> <important> <p>The <i>Value</i> and <i>Exists</i> parameters are deprecated. Even though DynamoDB will continue to support these parameters, we recommend that you use <i>AttributeValueList</i> and <i>ComparisonOperator</i> instead. <i>AttributeValueList</i> and <i>ComparisonOperator</i> let you construct a much wider range of conditions than is possible with <i>Value</i> and <i>Exists</i>.</p> </important>"
-    },
-    "FilterConditionMap":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"Condition"}
-    },
-    "GetItemInput":{
-      "type":"structure",
-      "required":[
-        "TableName",
-        "Key"
-      ],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table containing the requested item.</p>"
-        },
-        "Key":{
-          "shape":"Key",
-          "documentation":"<p>A map of attribute names to <i>AttributeValue</i> objects, representing the primary key of the item to retrieve.</p> <p>For the primary key, you must provide <i>all</i> of the attributes. For example, with a hash type primary key, you only need to specify the hash attribute. For a hash-and-range type primary key, you must specify <i>both</i> the hash attribute and the range attribute.</p>"
-        },
-        "AttributesToGet":{
-          "shape":"AttributeNameList",
-          "documentation":"<p>The names of one or more attributes to retrieve. If no attribute names are specified, then all attributes will be returned. If any of the requested attributes are not found, they will not appear in the result.</p> <p>Note that <i>AttributesToGet</i> has no effect on provisioned throughput consumption. DynamoDB determines capacity units consumed based on item size, not on the amount of data that is returned to an application.</p>"
-        },
-        "ConsistentRead":{
-          "shape":"ConsistentRead",
-          "documentation":"<p>If set to <code>true</code>, then the operation uses strongly consistent reads; otherwise, eventually consistent reads are used.</p>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"}
-      },
-      "documentation":"<p>Represents the input of a <i>GetItem</i> operation.</p>"
-    },
-    "GetItemOutput":{
-      "type":"structure",
-      "members":{
-        "Item":{
-          "shape":"AttributeMap",
-          "documentation":"<p>A map of attribute names to <i>AttributeValue</i> objects, as specified by <i>AttributesToGet</i>.</p>"
-        },
-        "ConsumedCapacity":{"shape":"ConsumedCapacity"}
-      },
-      "documentation":"<p>Represents the output of a <i>GetItem</i> operation.</p>"
-    },
-    "GlobalSecondaryIndex":{
-      "type":"structure",
-      "required":[
-        "IndexName",
-        "KeySchema",
-        "Projection",
-        "ProvisionedThroughput"
-      ],
-      "members":{
-        "IndexName":{
-          "shape":"IndexName",
-          "documentation":"<p>The name of the global secondary index. The name must be unique among all other indexes on this table.</p>"
-        },
-        "KeySchema":{
-          "shape":"KeySchema",
-          "documentation":"<p>The complete key schema for a global secondary index, which consists of one or more pairs of attribute names and key types (<code>HASH</code> or <code>RANGE</code>).</p>"
-        },
-        "Projection":{"shape":"Projection"},
-        "ProvisionedThroughput":{"shape":"ProvisionedThroughput"}
-      },
-      "documentation":"<p>Represents a global secondary index.</p>"
-    },
-    "GlobalSecondaryIndexDescription":{
-      "type":"structure",
-      "members":{
-        "IndexName":{
-          "shape":"IndexName",
-          "documentation":"<p>The name of the global secondary index.</p>"
-        },
-        "KeySchema":{
-          "shape":"KeySchema",
-          "documentation":"<p>The complete key schema for the global secondary index, consisting of one or more pairs of attribute names and key types (<code>HASH</code> or <code>RANGE</code>).</p>"
-        },
-        "Projection":{"shape":"Projection"},
-        "IndexStatus":{
-          "shape":"IndexStatus",
-          "documentation":"<p>The current state of the global secondary index:</p> <ul> <li> <p><i>CREATING</i> - The index is being created, as the result of a <i>CreateTable</i> or <i>UpdateTable</i> operation.</p> </li> <li> <p><i>UPDATING</i> - The index is being updated, as the result of a <i>CreateTable</i> or <i>UpdateTable</i> operation.</p> </li> <li> <p><i>DELETING</i> - The index is being deleted, as the result of a <i>DeleteTable</i> operation.</p> </li> <li> <p><i>ACTIVE</i> - The index is ready for use.</p> </li> </ul>"
-        },
-        "ProvisionedThroughput":{"shape":"ProvisionedThroughputDescription"},
-        "IndexSizeBytes":{
-          "shape":"Long",
-          "documentation":"<p>The total size of the specified index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p>"
-        },
-        "ItemCount":{
-          "shape":"Long",
-          "documentation":"<p>The number of items in the specified index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p>"
-        }
-      },
-      "documentation":"<p>Represents the properties of a global secondary index.</p>"
-    },
-    "GlobalSecondaryIndexDescriptionList":{
-      "type":"list",
-      "member":{"shape":"GlobalSecondaryIndexDescription"}
-    },
-    "GlobalSecondaryIndexList":{
-      "type":"list",
-      "member":{"shape":"GlobalSecondaryIndex"}
-    },
-    "GlobalSecondaryIndexUpdate":{
-      "type":"structure",
-      "members":{
-        "Update":{
-          "shape":"UpdateGlobalSecondaryIndexAction",
-          "documentation":"<p>The name of a global secondary index, along with the updated provisioned throughput settings that are to be applied to that index.</p>"
-        }
-      },
-      "documentation":"<p>Represents the new provisioned throughput settings to apply to a global secondary index.</p>"
-    },
-    "GlobalSecondaryIndexUpdateList":{
-      "type":"list",
-      "member":{"shape":"GlobalSecondaryIndexUpdate"}
-    },
-    "IndexName":{
-      "type":"string",
-      "min":3,
-      "max":255,
-      "pattern":"[a-zA-Z0-9_.-]+"
-    },
-    "IndexStatus":{
-      "type":"string",
-      "enum":[
-        "CREATING",
-        "UPDATING",
-        "DELETING",
-        "ACTIVE"
-      ]
-    },
-    "Integer":{"type":"integer"},
-    "InternalServerError":{
-      "type":"structure",
-      "members":{
-        "message":{
-          "shape":"ErrorMessage",
-          "documentation":"<p>The server encountered an internal error trying to fulfill the request.</p>"
-        }
-      },
-      "exception":true,
-      "fault":true,
-      "documentation":"<p>An error occurred on the server side.</p>"
-    },
-    "ItemCollectionKeyAttributeMap":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"AttributeValue"}
-    },
-    "ItemCollectionMetrics":{
-      "type":"structure",
-      "members":{
-        "ItemCollectionKey":{
-          "shape":"ItemCollectionKeyAttributeMap",
-          "documentation":"<p>The hash key value of the item collection. This is the same as the hash key of the item.</p>"
-        },
-        "SizeEstimateRangeGB":{
-          "shape":"ItemCollectionSizeEstimateRange",
-          "documentation":"<p>An estimate of item collection size, measured in gigabytes. This is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on that table. Use this estimate to measure whether a local secondary index is approaching its size limit.</p> <p>The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.</p>"
-        }
-      },
-      "documentation":"<p>Information about item collections, if any, that were affected by the operation. <i>ItemCollectionMetrics</i> is only returned if it was asked for in the request. If the table does not have any local secondary indexes, this information is not returned in the response.</p>"
-    },
-    "ItemCollectionMetricsMultiple":{
-      "type":"list",
-      "member":{"shape":"ItemCollectionMetrics"}
-    },
-    "ItemCollectionMetricsPerTable":{
-      "type":"map",
-      "key":{"shape":"TableName"},
-      "value":{"shape":"ItemCollectionMetricsMultiple"}
-    },
-    "ItemCollectionSizeEstimateBound":{"type":"double"},
-    "ItemCollectionSizeEstimateRange":{
-      "type":"list",
-      "member":{"shape":"ItemCollectionSizeEstimateBound"}
-    },
-    "ItemCollectionSizeLimitExceededException":{
-      "type":"structure",
-      "members":{
-        "message":{
-          "shape":"ErrorMessage",
-          "documentation":"<p>The total size of an item collection has exceeded the maximum limit of 10 gigabytes.</p>"
-        }
-      },
-      "exception":true,
-      "documentation":"<p>An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.</p>"
-    },
-    "ItemList":{
-      "type":"list",
-      "member":{"shape":"AttributeMap"}
-    },
-    "Key":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"AttributeValue"}
-    },
-    "KeyConditions":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"Condition"}
-    },
-    "KeyList":{
-      "type":"list",
-      "member":{"shape":"Key"},
-      "min":1,
-      "max":100
-    },
-    "KeySchema":{
-      "type":"list",
-      "member":{"shape":"KeySchemaElement"},
-      "min":1,
-      "max":2
-    },
-    "KeySchemaAttributeName":{
-      "type":"string",
-      "min":1,
-      "max":255
-    },
-    "KeySchemaElement":{
-      "type":"structure",
-      "required":[
-        "AttributeName",
-        "KeyType"
-      ],
-      "members":{
-        "AttributeName":{
-          "shape":"KeySchemaAttributeName",
-          "documentation":"<p>The name of a key attribute.</p>"
-        },
-        "KeyType":{
-          "shape":"KeyType",
-          "documentation":"<p>The attribute data, consisting of the data type and the attribute value itself.</p>"
-        }
-      },
-      "documentation":"<p>Represents <i>a single element</i> of a key schema. A key schema specifies the attributes that make up the primary key of a table, or the key attributes of an index.</p> <p>A <i>KeySchemaElement</i> represents exactly one attribute of the primary key. For example, a hash type primary key would be represented by one <i>KeySchemaElement</i>. A hash-and-range type primary key would require one <i>KeySchemaElement</i> for the hash attribute, and another <i>KeySchemaElement</i> for the range attribute.</p>"
-    },
-    "KeyType":{
-      "type":"string",
-      "enum":[
-        "HASH",
-        "RANGE"
-      ]
-    },
-    "KeysAndAttributes":{
-      "type":"structure",
-      "required":["Keys"],
-      "members":{
-        "Keys":{
-          "shape":"KeyList",
-          "documentation":"<p>The primary key attribute values that define the items and the attributes associated with the items.</p>"
-        },
-        "AttributesToGet":{
-          "shape":"AttributeNameList",
-          "documentation":"<p>One or more attributes to retrieve from the table or index. If no attribute names are specified then all attributes will be returned. If any of the specified attributes are not found, they will not appear in the result.</p>"
-        },
-        "ConsistentRead":{
-          "shape":"ConsistentRead",
-          "documentation":"<p>The consistency of a read operation. If set to <code>true</code>, then a strongly consistent read is used; otherwise, an eventually consistent read is used.</p>"
-        }
-      },
-      "documentation":"<p>Represents a set of primary keys and, for each key, the attributes to retrieve from the table.</p> <p>For each primary key, you must provide <i>all</i> of the key attributes. For example, with a hash type primary key, you only need to specify the hash attribute. For a hash-and-range type primary key, you must specify <i>both</i> the hash attribute and the range attribute.</p>"
-    },
-    "LimitExceededException":{
-      "type":"structure",
-      "members":{
-        "message":{
-          "shape":"ErrorMessage",
-          "documentation":"<p>Too many operations for a given subscriber.</p>"
-        }
-      },
-      "exception":true,
-      "documentation":"<p>The number of concurrent table requests (cumulative number of tables in the <code>CREATING</code>, <code>DELETING</code> or <code>UPDATING</code> state) exceeds the maximum allowed of 10.</p> <p>Also, for tables with secondary indexes, only one of those tables can be in the <code>CREATING</code> state at any point in time. Do not attempt to create more than one such table simultaneously.</p> <p>The total limit of tables in the <code>ACTIVE</code> state is 250.</p>"
-    },
-    "ListTablesInput":{
-      "type":"structure",
-      "members":{
-        "ExclusiveStartTableName":{
-          "shape":"TableName",
-          "documentation":"<p>The first table name that this operation will evaluate. Use the value that was returned for <i>LastEvaluatedTableName</i> in a previous operation, so that you can obtain the next page of results.</p>"
-        },
-        "Limit":{
-          "shape":"ListTablesInputLimit",
-          "documentation":"<p> A maximum number of table names to return. If this parameter is not specified, the limit is 100.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of a <i>ListTables</i> operation.</p>"
-    },
-    "ListTablesInputLimit":{
-      "type":"integer",
-      "min":1,
-      "max":100
-    },
-    "ListTablesOutput":{
-      "type":"structure",
-      "members":{
-        "TableNames":{
-          "shape":"TableNameList",
-          "documentation":"<p>The names of the tables associated with the current account at the current endpoint. The maximum size of this array is 100. </p> <p>If <i>LastEvaluatedTableName</i> also appears in the output, you can use this value as the <i>ExclusiveStartTableName</i> parameter in a subsequent <i>ListTables</i> request and obtain the next page of results.</p>"
-        },
-        "LastEvaluatedTableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the last table in the current page of results. Use this value as the <i>ExclusiveStartTableName</i> in a new request to obtain the next page of results, until all the table names are returned.</p> <p>If you do not receive a <i>LastEvaluatedTableName</i> value in the response, this means that there are no more table names to be retrieved.</p>"
-        }
-      },
-      "documentation":"<p>Represents the output of a <i>ListTables</i> operation.</p>"
-    },
-    "LocalSecondaryIndex":{
-      "type":"structure",
-      "required":[
-        "IndexName",
-        "KeySchema",
-        "Projection"
-      ],
-      "members":{
-        "IndexName":{
-          "shape":"IndexName",
-          "documentation":"<p>The name of the local secondary index. The name must be unique among all other indexes on this table.</p>"
-        },
-        "KeySchema":{
-          "shape":"KeySchema",
-          "documentation":"<p>The complete key schema for the local secondary index, consisting of one or more pairs of attribute names and key types (<code>HASH</code> or <code>RANGE</code>).</p>"
-        },
-        "Projection":{"shape":"Projection"}
-      },
-      "documentation":"<p>Represents a local secondary index.</p>"
-    },
-    "LocalSecondaryIndexDescription":{
-      "type":"structure",
-      "members":{
-        "IndexName":{
-          "shape":"IndexName",
-          "documentation":"<p>Represents the name of the local secondary index.</p>"
-        },
-        "KeySchema":{
-          "shape":"KeySchema",
-          "documentation":"The complete index key schema, which consists of one or more pairs of attribute names and key types (<code>HASH</code> or <code>RANGE</code>)."
-        },
-        "Projection":{"shape":"Projection"},
-        "IndexSizeBytes":{
-          "shape":"Long",
-          "documentation":"<p>The total size of the specified index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p>"
-        },
-        "ItemCount":{
-          "shape":"Long",
-          "documentation":"<p>The number of items in the specified index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p>"
-        }
-      },
-      "documentation":"<p>Represents the properties of a local secondary index.</p>"
-    },
-    "LocalSecondaryIndexDescriptionList":{
-      "type":"list",
-      "member":{"shape":"LocalSecondaryIndexDescription"}
-    },
-    "LocalSecondaryIndexList":{
-      "type":"list",
-      "member":{"shape":"LocalSecondaryIndex"}
-    },
-    "Long":{"type":"long"},
-    "NonKeyAttributeName":{
-      "type":"string",
-      "min":1,
-      "max":255
-    },
-    "NonKeyAttributeNameList":{
-      "type":"list",
-      "member":{"shape":"NonKeyAttributeName"},
-      "min":1,
-      "max":20
-    },
-    "NumberAttributeValue":{"type":"string"},
-    "NumberSetAttributeValue":{
-      "type":"list",
-      "member":{"shape":"NumberAttributeValue"}
-    },
-    "PositiveIntegerObject":{
-      "type":"integer",
-      "min":1
-    },
-    "PositiveLongObject":{
-      "type":"long",
-      "min":1
-    },
-    "Projection":{
-      "type":"structure",
-      "members":{
-        "ProjectionType":{
-          "shape":"ProjectionType",
-          "documentation":"<p>The set of attributes that are projected into the index:</p> <ul> <li> <p><code>KEYS_ONLY</code> - Only the index and primary keys are projected into the index.</p> </li> <li> <p><code>INCLUDE</code> - Only the specified table attributes are projected into the index. The list of projected attributes are in <i>NonKeyAttributes</i>.</p> </li> <li> <p><code>ALL</code> - All of the table attributes are projected into the index.</p> </li> </ul>"
-        },
-        "NonKeyAttributes":{
-          "shape":"NonKeyAttributeNameList",
-          "documentation":"<p>Represents the non-key attribute names which will be projected into the index.</p> <p>For local secondary indexes, the total count of <i>NonKeyAttributes</i> summed across all of the local secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total.</p>"
-        }
-      },
-      "documentation":"<p>Represents attributes that are copied (projected) from the table into an index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.</p>"
-    },
-    "ProjectionType":{
-      "type":"string",
-      "enum":[
-        "ALL",
-        "KEYS_ONLY",
-        "INCLUDE"
-      ]
-    },
-    "ProvisionedThroughput":{
-      "type":"structure",
-      "required":[
-        "ReadCapacityUnits",
-        "WriteCapacityUnits"
-      ],
-      "members":{
-        "ReadCapacityUnits":{
-          "shape":"PositiveLongObject",
-          "documentation":"<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <i>ThrottlingException</i>. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#ProvisionedThroughput\">Specifying Read and Write Requirements</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "WriteCapacityUnits":{
-          "shape":"PositiveLongObject",
-          "documentation":"<p>The maximum number of writes consumed per second before DynamoDB returns a <i>ThrottlingException</i>. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#ProvisionedThroughput\">Specifying Read and Write Requirements</a> in the Amazon DynamoDB Developer Guide.</p>"
-        }
-      },
-      "documentation":"<p>Represents the provisioned throughput settings for a specified table or index. The settings can be modified using the <i>UpdateTable</i> operation.</p> <p>For current minimum and maximum provisioned throughput values, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html\">Limits</a> in the Amazon DynamoDB Developer Guide.</p>"
-    },
-    "ProvisionedThroughputDescription":{
-      "type":"structure",
-      "members":{
-        "LastIncreaseDateTime":{
-          "shape":"Date",
-          "documentation":"<p>The date and time of the last provisioned throughput increase for this table.</p>"
-        },
-        "LastDecreaseDateTime":{
-          "shape":"Date",
-          "documentation":"<p>The date and time of the last provisioned throughput decrease for this table.</p>"
-        },
-        "NumberOfDecreasesToday":{
-          "shape":"PositiveLongObject",
-          "documentation":"<p>The number of provisioned throughput decreases for this table during this UTC calendar day. For current maximums on provisioned throughput decreases, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html\">Limits</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "ReadCapacityUnits":{
-          "shape":"PositiveLongObject",
-          "documentation":"<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <i>ThrottlingException</i>. Eventually consistent reads require less effort than strongly consistent reads, so a setting of 50 <i>ReadCapacityUnits</i> per second provides 100 eventually consistent <i>ReadCapacityUnits</i> per second.</p>"
-        },
-        "WriteCapacityUnits":{
-          "shape":"PositiveLongObject",
-          "documentation":"<p>The maximum number of writes consumed per second before DynamoDB returns a <i>ThrottlingException</i>.</p>"
-        }
-      },
-      "documentation":"<p>Represents the provisioned throughput settings for the table, consisting of read and write capacity units, along with data about increases and decreases.</p>"
-    },
-    "ProvisionedThroughputExceededException":{
-      "type":"structure",
-      "members":{
-        "message":{
-          "shape":"ErrorMessage",
-          "documentation":"<p>You exceeded your maximum allowed provisioned throughput.</p>"
-        }
-      },
-      "exception":true,
-      "documentation":"<p>The request rate is too high, or the request is too large, for the available throughput to accommodate. The AWS SDKs automatically retry requests that receive this exception; therefore, your request will eventually succeed, unless the request is too large or your retry queue is too large to finish. Reduce the frequency of requests by using the strategies listed in <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#APIRetries\">Error Retries and Exponential Backoff</a> in the Amazon DynamoDB Developer Guide.</p>"
-    },
-    "PutItemInput":{
-      "type":"structure",
-      "required":[
-        "TableName",
-        "Item"
-      ],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table to contain the item.</p>"
-        },
-        "Item":{
-          "shape":"PutItemInputAttributeMap",
-          "documentation":"<p>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.</p> <p>You must provide <i>all</i> of the attributes for the primary key. For example, with a hash type primary key, you only need to specify the hash attribute. For a hash-and-range type primary key, you must specify <i>both</i> the hash attribute and the range attribute.</p> <p>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.</p> <p>For more information about primary keys, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataModel.html#DataModelPrimaryKey\">Primary Key</a> in the Amazon DynamoDB Developer Guide.</p> <p>Each element in the <i>Item</i> map is an <i>AttributeValue</i> object.</p>"
-        },
-        "Expected":{
-          "shape":"ExpectedAttributeMap",
-          "documentation":"<p>A map of attribute/condition pairs. This is the conditional block for the <i>PutItem</i> operation.</p> <p>Each element of <i>Expected</i> consists of an attribute name, a comparison operator, and one or more values. DynamoDB compares the attribute with the value(s) you supplied, using the comparison operator. For each <i>Expected</i> element, the result of the evaluation is either true or false.</p> <p>If you specify more than one element in the <i>Expected</i> map, then by default all of the conditions must evaluate to true. In other words, the conditions are ANDed together. (You can use the <i>ConditionalOperator</i> parameter to OR the conditions instead. If you do this, then at least one of the conditions must evaluate to true, rather than all of them.)</p> <p>If the <i>Expected</i> map evaluates to true, then the conditional operation succeeds; otherwise, it fails.</p> <p>Each item in <i>Expected</i> represents an attribute name for DynamoDB to check, along with an <i>AttributeValueList</i> and a <i>ComparisonOperator</i>:</p> <ul> <li> <p><i>AttributeValueList</i> - One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\" >http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p> </li> <li> <p><i>ComparisonOperator</i> - A comparator for evaluating attributes in the <i>AttributeValueList</i>. When performing the comparison, DynamoDB uses strongly consistent reads.</p> <p>The following comparison operators are available:</p> <p><code>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</code></p> <p>The following are descriptions of each comparison operator.</p> <ul> <li> <p><code>EQ</code> : Equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NE</code> : Not equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LE</code> : Less than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LT</code> : Less than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GE</code> : Greater than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GT</code> : Greater than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NOT_NULL</code> : The attribute exists. </p> </li> <li> <p><code>NULL</code> : The attribute does not exist. </p> </li> <li> <p><code>CONTAINS</code> : checks for a subsequence, or value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for a substring match. If the target attribute of the comparison is Binary, then the operation looks for a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for a member of the set (not as a substring).</p> </li> <li> <p><code>NOT_CONTAINS</code> : checks for absence of a subsequence, or absence of a value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for the absence of a substring match. If the target attribute of the comparison is Binary, then the operation checks for the absence of a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for the absence of a member of the set (not as a substring).</p></li> <li> <p><code>BEGINS_WITH</code> : checks for a prefix. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String or Binary (not a Number or a set). The target attribute of the comparison must be a String or Binary (not a Number or a set).</p> <p/> </li> <li> <p><code>IN</code> : checks for exact matches.</p> <p><i>AttributeValueList</i> can contain more than one <i>AttributeValue</i> of type String, Number, or Binary (not a set). The target attribute of the comparison must be of the same type and exact value to match. A String never matches a String set.</p> </li> <li> <p><code>BETWEEN</code> : Greater than or equal to the first value, and less than or equal to the second value. </p> <p><i>AttributeValueList</i> must contain two <i>AttributeValue</i> elements of the same type, either String, Number, or Binary (not a set). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not compare to <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code></p> </li> </ul> </li> </ul> <p>For usage examples of <i>AttributeValueList</i> and <i>ComparisonOperator</i>, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html#ConditionalExpressions\" >Conditional Expressions</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "ReturnValues":{
-          "shape":"ReturnValue",
-          "documentation":"<p>Use <i>ReturnValues</i> if you want to get the item attributes as they appeared before they were updated with the <i>PutItem</i> request. For <i>PutItem</i>, the valid values are:</p> <ul> <li> <p><code>NONE</code> - If <i>ReturnValues</i> is not specified, or if its value is <code>NONE</code>, then nothing is returned. (This is the default for <i>ReturnValues</i>.)</p> </li> <li> <p><code>ALL_OLD</code> - If <i>PutItem</i> overwrote an attribute name-value pair, then the content of the old item is returned.</p> </li> </ul>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"},
-        "ReturnItemCollectionMetrics":{
-          "shape":"ReturnItemCollectionMetrics",
-          "documentation":"<p>If set to <code>SIZE</code>, statistics about item collections, if any, that were modified during the operation are returned in the response. If set to <code>NONE</code> (the default), no statistics are returned.</p>"
-        },
-        "ConditionalOperator":{
-          "shape":"ConditionalOperator",
-          "documentation":"<p>A logical operator to apply to the conditions in the <i>Expected</i> map:</p> <ul> <li><p><code>AND</code> - If <i>all</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> <li><p><code>OR</code> - If <i>at least one</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> </ul> <p>If you omit <i>ConditionalOperator</i>, then <code>AND</code> is the default.</p> <p>The operation will succeed only if the entire map evaluates to true.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of a <i>PutItem</i> operation.</p>"
-    },
-    "PutItemInputAttributeMap":{
-      "type":"map",
-      "key":{"shape":"AttributeName"},
-      "value":{"shape":"AttributeValue"}
-    },
-    "PutItemOutput":{
-      "type":"structure",
-      "members":{
-        "Attributes":{
-          "shape":"AttributeMap",
-          "documentation":"<p>The attribute values as they appeared before the <i>PutItem</i> operation, but only if <i>ReturnValues</i> is specified as <code>ALL_OLD</code> in the request. Each element consists of an attribute name and an attribute value.</p>"
-        },
-        "ConsumedCapacity":{"shape":"ConsumedCapacity"},
-        "ItemCollectionMetrics":{
-          "shape":"ItemCollectionMetrics",
-          "documentation":"<p>Information about item collections, if any, that were affected by the operation. <i>ItemCollectionMetrics</i> is only returned if it was asked for in the request. If the table does not have any local secondary indexes, this information is not returned in the response.</p> <p>Each <i>ItemCollectionMetrics</i> element consists of:</p> <ul> <li><p><i>ItemCollectionKey</i> - The hash key value of the item collection. This is the same as the hash key of the item.</p></li> <li><p><i>SizeEstimateRange</i> - An estimate of item collection size, measured in gigabytes. This is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on that table. Use this estimate to measure whether a local secondary index is approaching its size limit.</p> <p>The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.</p> </li> </ul>"
-        }
-      },
-      "documentation":"<p>Represents the output of a <i>PutItem</i> operation.</p>"
-    },
-    "PutRequest":{
-      "type":"structure",
-      "required":["Item"],
-      "members":{
-        "Item":{
-          "shape":"PutItemInputAttributeMap",
-          "documentation":"<p>A map of attribute name to attribute values, representing the primary key of an item to be processed by <i>PutItem</i>. All of the table's primary key attributes must be specified, and their data types must match those of the table's key schema. If any attributes are present in the item which are part of an index key schema for the table, their types must match the index key schema.</p>"
-        }
-      },
-      "documentation":"<p>Represents a request to perform a <i>PutItem</i> operation on an item.</p>"
-    },
-    "QueryInput":{
-      "type":"structure",
-      "required":[
-        "TableName",
-        "KeyConditions"
-      ],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table containing the requested items. </p>"
-        },
-        "IndexName":{
-          "shape":"IndexName",
-          "documentation":"<p>The name of an index to query. This can be any local secondary index or global secondary index on the table.</p>"
-        },
-        "Select":{
-          "shape":"Select",
-          "documentation":"<p>The attributes to be returned in the result. You can retrieve all item attributes, specific item attributes, the count of matching items, or in the case of an index, some or all of the attributes projected into the index.</p> <ul> <li> <p><code>ALL_ATTRIBUTES</code>: Returns all of the item attributes from the specified table or index. If you are querying a local secondary index, then for each matching item in the index DynamoDB will fetch the entire item from the parent table. If the index is configured to project all item attributes, then all of the data can be obtained from the local secondary index, and no fetching is required..</p> </li> <li> <p><code>ALL_PROJECTED_ATTRIBUTES</code>: Allowed only when querying an index. Retrieves all attributes which have been projected into the index. If the index is configured to project all attributes, this is equivalent to specifying <code>ALL_ATTRIBUTES</code>.</p> </li> <li> <p><code>COUNT</code>: Returns the number of matching items, rather than the matching items themselves.</p> </li> <li> <p> <code>SPECIFIC_ATTRIBUTES</code> : Returns only the attributes listed in <i>AttributesToGet</i>. This is equivalent to specifying <i>AttributesToGet</i> without specifying any value for <i>Select</i>.</p> <p>If you are querying a local secondary index and request only attributes that are projected into that index, the operation will read only the index and not the table. If any of the requested attributes are not projected into the local secondary index, DynamoDB will fetch each of these attributes from the parent table. This extra fetching incurs additional throughput cost and latency.</p> <p>If you are querying a global secondary index, you can only request attributes that are projected into the index. Global secondary index queries cannot fetch attributes from the parent table.</p> </li> </ul> <p>If neither <i>Select</i> nor <i>AttributesToGet</i> are specified, DynamoDB defaults to <code>ALL_ATTRIBUTES</code> when accessing a table, and <code>ALL_PROJECTED_ATTRIBUTES</code> when accessing an index. You cannot use both <i>Select</i> and <i>AttributesToGet</i> together in a single request, <i>unless</i> the value for <i>Select</i> is <code>SPECIFIC_ATTRIBUTES</code>. (This usage is equivalent to specifying <i>AttributesToGet</i> without any value for <i>Select</i>.)</p>"
-        },
-        "AttributesToGet":{
-          "shape":"AttributeNameList",
-          "documentation":"<p>The names of one or more attributes to retrieve. If no attribute names are specified, then all attributes will be returned. If any of the requested attributes are not found, they will not appear in the result.</p> <p>Note that <i>AttributesToGet</i> has no effect on provisioned throughput consumption. DynamoDB determines capacity units consumed based on item size, not on the amount of data that is returned to an application.</p> <p>You cannot use both <i>AttributesToGet</i> and <i>Select</i> together in a <i>Query</i> request, <i>unless</i> the value for <i>Select</i> is <code>SPECIFIC_ATTRIBUTES</code>. (This usage is equivalent to specifying <i>AttributesToGet</i> without any value for <i>Select</i>.)</p> <p>If you are querying a local secondary index and request only attributes that are projected into that index, the operation will read only the index and not the table. If any of the requested attributes are not projected into the local secondary index, DynamoDB will fetch each of these attributes from the parent table. This extra fetching incurs additional throughput cost and latency.</p> <p>If you are querying a global secondary index, you can only request attributes that are projected into the index. Global secondary index queries cannot fetch attributes from the parent table.</p>"
-        },
-        "Limit":{
-          "shape":"PositiveIntegerObject",
-          "documentation":"<p>The maximum number of items to evaluate (not necessarily the number of matching items). If DynamoDB processes the number of items up to the limit while processing the results, it stops the operation and returns the matching values up to that point, and a <i>LastEvaluatedKey</i> to apply in a subsequent operation, so that you can pick up where you left off. Also, if the processed data set size exceeds 1 MB before DynamoDB reaches this limit, it stops the operation and returns the matching values up to the limit, and a <i>LastEvaluatedKey</i> to apply in a subsequent operation to continue the operation. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html\" >Query and Scan</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "ConsistentRead":{
-          "shape":"ConsistentRead",
-          "documentation":"<p>If set to <code>true</code>, then the operation uses strongly consistent reads; otherwise, eventually consistent reads are used.</p> <p>Strongly consistent reads are not supported on global secondary indexes. If you query a global secondary index with <i>ConsistentRead</i> set to <code>true</code>, you will receive an error message.</p>"
-        },
-        "KeyConditions":{
-          "shape":"KeyConditions",
-          "documentation":"<p>The selection criteria for the query.</p> <p>For a query on a table, you can only have conditions on the table primary key attributes. You <i>must</i> specify the hash key attribute name and value as an <code>EQ</code> condition. You can <i>optionally</i> specify a second condition, referring to the range key attribute.</p> <p>For a query on an index, you can only have conditions on the index key attributes. You <i>must</i> specify the index hash attribute name and value as an EQ condition. You can <i>optionally</i> specify a second condition, referring to the index key range attribute.</p> <p>If you specify more than one condition in the <i>KeyConditions</i> map, then by default all of the conditions must evaluate to true. In other words, the conditions are ANDed together. (You can use the <i>ConditionalOperator</i> parameter to OR the conditions instead. If you do this, then at least one of the conditions must evaluate to true, rather than all of them.)</p> <p>Each <i>KeyConditions</i> element consists of an attribute name to compare, along with the following:</p> <ul> <li> <p><i>AttributeValueList</i> - One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\">http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p> </li> <li> <p><i>ComparisonOperator</i> - A comparator for evaluating attributes. For example, equals, greater than, less than, etc.</p> <p>For <i>KeyConditions</i>, only the following comparison operators are supported:</p> <p> <code>EQ | LE | LT | GE | GT | BEGINS_WITH | BETWEEN</code> </p> <p>The following are descriptions of these comparison operators.</p> <ul> <li> <p><code>EQ</code> : Equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p></p> </li> <li> <p><code>LE</code> : Less than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LT</code> : Less than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GE</code> : Greater than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GT</code> : Greater than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>BEGINS_WITH</code> : checks for a prefix. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String or Binary (not a Number or a set). The target attribute of the comparison must be a String or Binary (not a Number or a set).</p> <p/> </li> <li> <p><code>BETWEEN</code> : Greater than or equal to the first value, and less than or equal to the second value. </p> <p><i>AttributeValueList</i> must contain two <i>AttributeValue</i> elements of the same type, either String, Number, or Binary (not a set). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not compare to <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code></p> </li> </ul> </li> </ul> <p>For usage examples of <i>AttributeValueList</i> and <i>ComparisonOperator</i>, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html#ConditionalExpressions\">Conditional Expressions</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "QueryFilter":{
-          "shape":"FilterConditionMap",
-          "documentation":"<p>Evaluates the query results and returns only the desired values.</p> <p>If you specify more than one condition in the <i>QueryFilter</i> map, then by default all of the conditions must evaluate to true. In other words, the conditions are ANDed together. (You can use the <i>ConditionalOperator</i> parameter to OR the conditions instead. If you do this, then at least one of the conditions must evaluate to true, rather than all of them.)</p> <p>Each <i>QueryFilter</i> element consists of an attribute name to compare, along with the following:</p> <ul> <li> <p><i>AttributeValueList</i> - One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\">http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p> <p>For information on specifying data types in JSON, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataFormat.html\">JSON Data Format</a> in the Amazon DynamoDB Developer Guide.</p> </li> <li> <p><i>ComparisonOperator</i> - A comparator for evaluating attributes. For example, equals, greater than, less than, etc.</p> <p>The following comparison operators are available:</p> <p><code>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</code></p> <p>For complete descriptions of all comparison operators, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Condition.html\">API_Condition.html</a>.</p> </li> </ul>"
-        },
-        "ConditionalOperator":{
-          "shape":"ConditionalOperator",
-          "documentation":"<p>A logical operator to apply to the conditions in the <i>QueryFilter</i> map:</p> <ul> <li><p><code>AND</code> - If <i>all</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> <li><p><code>OR</code> - If <i>at least one</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> </ul> <p>If you omit <i>ConditionalOperator</i>, then <code>AND</code> is the default.</p> <p>The operation will succeed only if the entire map evaluates to true.</p>"
-        },
-        "ScanIndexForward":{
-          "shape":"BooleanObject",
-          "documentation":"<p>Specifies ascending (true) or descending (false) traversal of the index. DynamoDB returns results reflecting the requested order determined by the range key. If the data type is Number, the results are returned in numeric order. For String, the results are returned in order of ASCII character code values. For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values.</p> <p>If <i>ScanIndexForward</i> is not specified, the results are returned in ascending order.</p>"
-        },
-        "ExclusiveStartKey":{
-          "shape":"Key",
-          "documentation":"<p>The primary key of the first item that this operation will evaluate. Use the value that was returned for <i>LastEvaluatedKey</i> in the previous operation.</p> <p>The data type for <i>ExclusiveStartKey</i> must be String, Number or Binary. No set data types are allowed.</p>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"}
-      },
-      "documentation":"<p>Represents the input of a <i>Query</i> operation.</p>"
-    },
-    "QueryOutput":{
-      "type":"structure",
-      "members":{
-        "Items":{
-          "shape":"ItemList",
-          "documentation":"<p>An array of item attributes that match the query criteria. Each element in this array consists of an attribute name and the value for that attribute.</p>"
-        },
-        "Count":{
-          "shape":"Integer",
-          "documentation":"<p>The number of items in the response.</p> <p>If you used a <i>QueryFilter</i> in the request, then <i>Count</i> is the number of items returned <i>after</i> the filter was applied, and <i>ScannedCount</i> is the number of matching items <i>before</i> the filter was applied.</p> <p>If you did not use a filter in the request, then <i>Count</i> and <i>ScannedCount</i> are the same.</p>"
-        },
-        "ScannedCount":{
-          "shape":"Integer",
-          "documentation":"<p>The number of items evaluated, <i>before</i> any <i>QueryFilter</i> is applied. A high <i>ScannedCount</i> value with few, or no, <i>Count</i> results indicates an inefficient <i>Query</i> operation. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html#Count\">Count and ScannedCount</a> in the Amazon DynamoDB Developer Guide.</p> <p>If you did not use a filter in the request, then <i>ScannedCount</i> is the same as <i>Count</i>.</p>"
-        },
-        "LastEvaluatedKey":{
-          "shape":"Key",
-          "documentation":"<p>The primary key of the item where the operation stopped, inclusive of the previous result set. Use this value to start a new operation, excluding this value in the new request.</p> <p>If <i>LastEvaluatedKey</i> is empty, then the \"last page\" of results has been processed and there is no more data to be retrieved.</p> <p>If <i>LastEvaluatedKey</i> is not empty, this does not necessarily mean that there is more data in the result set. The only way to know when you have reached the end of the result set is when <i>LastEvaluatedKey</i> is empty.</p>"
-        },
-        "ConsumedCapacity":{"shape":"ConsumedCapacity"}
-      },
-      "documentation":"<p>Represents the output of a <i>Query</i> operation.</p>"
-    },
-    "ResourceInUseException":{
-      "type":"structure",
-      "members":{
-        "message":{
-          "shape":"ErrorMessage",
-          "documentation":"<p>The resource which is being attempted to be changed is in use.</p>"
-        }
-      },
-      "exception":true,
-      "documentation":"<p>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 <code>CREATING</code> state.</p>"
-    },
-    "ResourceNotFoundException":{
-      "type":"structure",
-      "members":{
-        "message":{
-          "shape":"ErrorMessage",
-          "documentation":"<p>The resource which is being requested does not exist.</p>"
-        }
-      },
-      "exception":true,
-      "documentation":"<p>The operation tried to access a nonexistent table or index. The resource may not be specified correctly, or its status may not be <code>ACTIVE</code>.</p>"
-    },
-    "ReturnConsumedCapacity":{
-      "type":"string",
-      "enum":[
-        "INDEXES",
-        "TOTAL",
-        "NONE"
-      ],
-      "documentation":"<p>If set to <code>TOTAL</code>, the response includes <i>ConsumedCapacity</i> data for tables and indexes. If set to <code>INDEXES</code>, the response includes <i>ConsumedCapacity</i> for indexes. If set to <code>NONE</code> (the default), <i>ConsumedCapacity</i> is not included in the response.</p>"
-    },
-    "ReturnItemCollectionMetrics":{
-      "type":"string",
-      "enum":[
-        "SIZE",
-        "NONE"
-      ]
-    },
-    "ReturnValue":{
-      "type":"string",
-      "enum":[
-        "NONE",
-        "ALL_OLD",
-        "UPDATED_OLD",
-        "ALL_NEW",
-        "UPDATED_NEW"
-      ]
-    },
-    "ScalarAttributeType":{
-      "type":"string",
-      "enum":[
-        "S",
-        "N",
-        "B"
-      ]
-    },
-    "ScanInput":{
-      "type":"structure",
-      "required":["TableName"],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table containing the requested items.</p>"
-        },
-        "AttributesToGet":{
-          "shape":"AttributeNameList",
-          "documentation":"<p>The names of one or more attributes to retrieve. If no attribute names are specified, then all attributes will be returned. If any of the requested attributes are not found, they will not appear in the result.</p> <p>Note that <i>AttributesToGet</i> has no effect on provisioned throughput consumption. DynamoDB determines capacity units consumed based on item size, not on the amount of data that is returned to an application.</p>"
-        },
-        "Limit":{
-          "shape":"PositiveIntegerObject",
-          "documentation":"<p>The maximum number of items to evaluate (not necessarily the number of matching items). If DynamoDB processes the number of items up to the limit while processing the results, it stops the operation and returns the matching values up to that point, and a <i>LastEvaluatedKey</i> to apply in a subsequent operation, so that you can pick up where you left off. Also, if the processed data set size exceeds 1 MB before DynamoDB reaches this limit, it stops the operation and returns the matching values up to the limit, and a <i>LastEvaluatedKey</i> to apply in a subsequent operation to continue the operation. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html\" >Query and Scan</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "Select":{
-          "shape":"Select",
-          "documentation":"<p>The attributes to be returned in the result. You can retrieve all item attributes, specific item attributes, or the count of matching items.</p> <ul> <li> <p><code>ALL_ATTRIBUTES</code>: Returns all of the item attributes.</p> </li> <li> <p><code>COUNT</code>: Returns the number of matching items, rather than the matching items themselves.</p> </li> <li> <p> <code>SPECIFIC_ATTRIBUTES</code> : Returns only the attributes listed in <i>AttributesToGet</i>. This is equivalent to specifying <i>AttributesToGet</i> without specifying any value for <i>Select</i>.</p> </li> </ul> <p>If neither <i>Select</i> nor <i>AttributesToGet</i> are specified, DynamoDB defaults to <code>ALL_ATTRIBUTES</code>. You cannot use both <i>Select</i> and <i>AttributesToGet</i> together in a single request, <i>unless</i> the value for <i>Select</i> is <code>SPECIFIC_ATTRIBUTES</code>. (This usage is equivalent to specifying <i>AttributesToGet</i> without any value for <i>Select</i>.)</p>"
-        },
-        "ScanFilter":{
-          "shape":"FilterConditionMap",
-          "documentation":"<p>Evaluates the scan results and returns only the desired values.</p> <p>If you specify more than one condition in the <i>ScanFilter</i> map, then by default all of the conditions must evaluate to true. In other words, the conditions are ANDed together. (You can use the <i>ConditionalOperator</i> parameter to OR the conditions instead. If you do this, then at least one of the conditions must evaluate to true, rather than all of them.)</p> <p>Each <i>ScanFilter</i> element consists of an attribute name to compare, along with the following:</p> <ul> <li> <p><i>AttributeValueList</i> - One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\">http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p> <p>For information on specifying data types in JSON, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataFormat.html\">JSON Data Format</a> in the Amazon DynamoDB Developer Guide.</p> </li> <li> <p><i>ComparisonOperator</i> - A comparator for evaluating attributes. For example, equals, greater than, less than, etc.</p> <p>The following comparison operators are available:</p> <p><code>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</code></p> <p>For complete descriptions of all comparison operators, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Condition.html\">Condition</a>.</p> </li> </ul>"
-        },
-        "ConditionalOperator":{
-          "shape":"ConditionalOperator",
-          "documentation":"<p>A logical operator to apply to the conditions in the <i>ScanFilter</i> map:</p> <ul> <li><p><code>AND</code> - If <i>all</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> <li><p><code>OR</code> - If <i>at least one</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> </ul> <p>If you omit <i>ConditionalOperator</i>, then <code>AND</code> is the default.</p> <p>The operation will succeed only if the entire map evaluates to true.</p>"
-        },
-        "ExclusiveStartKey":{
-          "shape":"Key",
-          "documentation":"<p>The primary key of the first item that this operation will evaluate. Use the value that was returned for <i>LastEvaluatedKey</i> in the previous operation.</p> <p>The data type for <i>ExclusiveStartKey</i> must be String, Number or Binary. No set data types are allowed.</p> <p>In a parallel scan, a <i>Scan</i> request that includes <i>ExclusiveStartKey</i> must specify the same segment whose previous <i>Scan</i> returned the corresponding value of <i>LastEvaluatedKey</i>.</p>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"},
-        "TotalSegments":{
-          "shape":"ScanTotalSegments",
-          "documentation":"<p>For a parallel <i>Scan</i> request, <i>TotalSegments</i> represents the total number of segments into which the <i>Scan</i> operation will be divided. The value of <i>TotalSegments</i> corresponds to the number of application workers that will perform the parallel scan. For example, if you want to scan a table using four application threads, you would specify a <i>TotalSegments</i> value of 4.</p> <p>The value for <i>TotalSegments</i> must be greater than or equal to 1, and less than or equal to 4096. If you specify a <i>TotalSegments</i> value of 1, the <i>Scan</i> will be sequential rather than parallel.</p> <p>If you specify <i>TotalSegments</i>, you must also specify <i>Segment</i>.</p>"
-        },
-        "Segment":{
-          "shape":"ScanSegment",
-          "documentation":"<p>For a parallel <i>Scan</i> request, <i>Segment</i> identifies an individual segment to be scanned by an application worker.</p> <p>Segment IDs are zero-based, so the first segment is always 0. For example, if you want to scan a table using four application threads, the first thread would specify a <i>Segment</i> value of 0, the second thread would specify 1, and so on.</p> <p>The value of <i>LastEvaluatedKey</i> returned from a parallel <i>Scan</i> request must be used as <i>ExclusiveStartKey</i> with the same Segment ID in a subsequent <i>Scan</i> operation.</p> <p>The value for <i>Segment</i> must be greater than or equal to 0, and less than the value provided for <i>TotalSegments</i>.</p> <p>If you specify <i>Segment</i>, you must also specify <i>TotalSegments</i>.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of a <i>Scan</i> operation.</p>"
-    },
-    "ScanOutput":{
-      "type":"structure",
-      "members":{
-        "Items":{
-          "shape":"ItemList",
-          "documentation":"<p>An array of item attributes that match the scan criteria. Each element in this array consists of an attribute name and the value for that attribute.</p>"
-        },
-        "Count":{
-          "shape":"Integer",
-          "documentation":"<p>The number of items in the response.</p> <p>If you used a <i>ScanFilter</i> in the request, then <i>Count</i> is the number of items returned <i>after</i> the filter was applied, and <i>ScannedCount</i> is the number of matching items <i>before</i> the filter was applied.</p> <p>If you did not use a filter in the request, then <i>Count</i> is the same as <i>ScannedCount</i>.</p>"
-        },
-        "ScannedCount":{
-          "shape":"Integer",
-          "documentation":"<p>The number of items evaluated, <i>before</i> any <i>ScanFilter</i> is applied. A high <i>ScannedCount</i> value with few, or no, <i>Count</i> results indicates an inefficient <i>Scan</i> operation. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html#Count\">Count and ScannedCount</a> in the Amazon DynamoDB Developer Guide.</p> <p>If you did not use a filter in the request, then <i>ScannedCount</i> is the same as <i>Count</i>.</p>"
-        },
-        "LastEvaluatedKey":{
-          "shape":"Key",
-          "documentation":"<p>The primary key of the item where the operation stopped, inclusive of the previous result set. Use this value to start a new operation, excluding this value in the new request.</p> <p>If <i>LastEvaluatedKey</i> is empty, then the \"last page\" of results has been processed and there is no more data to be retrieved.</p> <p>If <i>LastEvaluatedKey</i> is not empty, this does not necessarily mean that there is more data in the result set. The only way to know when you have reached the end of the result set is when <i>LastEvaluatedKey</i> is empty.</p>"
-        },
-        "ConsumedCapacity":{"shape":"ConsumedCapacity"}
-      },
-      "documentation":"<p>Represents the output of a <i>Scan</i> operation.</p>"
-    },
-    "ScanSegment":{
-      "type":"integer",
-      "min":0,
-      "max":999999
-    },
-    "ScanTotalSegments":{
-      "type":"integer",
-      "min":1,
-      "max":1000000
-    },
-    "SecondaryIndexesCapacityMap":{
-      "type":"map",
-      "key":{"shape":"IndexName"},
-      "value":{"shape":"Capacity"}
-    },
-    "Select":{
-      "type":"string",
-      "enum":[
-        "ALL_ATTRIBUTES",
-        "ALL_PROJECTED_ATTRIBUTES",
-        "SPECIFIC_ATTRIBUTES",
-        "COUNT"
-      ]
-    },
-    "StringAttributeValue":{"type":"string"},
-    "StringSetAttributeValue":{
-      "type":"list",
-      "member":{"shape":"StringAttributeValue"}
-    },
-    "TableDescription":{
-      "type":"structure",
-      "members":{
-        "AttributeDefinitions":{
-          "shape":"AttributeDefinitions",
-          "documentation":"<p>An array of <i>AttributeDefinition</i> objects. Each of these objects describes one attribute in the table and index key schema.</p> <p>Each <i>AttributeDefinition</i> object in this array is composed of:</p> <ul> <li> <p><i>AttributeName</i> - The name of the attribute.</p> </li> <li> <p><i>AttributeType</i> - The data type for the attribute.</p> </li> </ul>"
-        },
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table.</p>"
-        },
-        "KeySchema":{
-          "shape":"KeySchema",
-          "documentation":"<p>The primary key structure for the table. Each <i>KeySchemaElement</i> consists of:</p> <ul> <li> <p><i>AttributeName</i> - The name of the attribute.</p> </li> <li> <p><i>KeyType</i> - The key type for the attribute. Can be either <code>HASH</code> or <code>RANGE</code>.</p> </li> </ul> <p>For more information about primary keys, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataModel.html#DataModelPrimaryKey\">Primary Key</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "TableStatus":{
-          "shape":"TableStatus",
-          "documentation":"<p>The current state of the table:</p> <ul> <li> <p><i>CREATING</i> - The table is being created, as the result of a <i>CreateTable</i> operation.</p> </li> <li> <p><i>UPDATING</i> - The table is being updated, as the result of an <i>UpdateTable</i> operation.</p> </li> <li> <p><i>DELETING</i> - The table is being deleted, as the result of a <i>DeleteTable</i> operation.</p> </li> <li> <p><i>ACTIVE</i> - The table is ready for use.</p> </li> </ul>"
-        },
-        "CreationDateTime":{
-          "shape":"Date",
-          "documentation":"<p>The date and time when the table was created, in <a href=\"http://www.epochconverter.com/\">UNIX epoch time</a> format.</p>"
-        },
-        "ProvisionedThroughput":{
-          "shape":"ProvisionedThroughputDescription",
-          "documentation":"<p>The provisioned throughput settings for the table, consisting of read and write capacity units, along with data about increases and decreases.</p>"
-        },
-        "TableSizeBytes":{
-          "shape":"Long",
-          "documentation":"<p>The total size of the specified table, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p>"
-        },
-        "ItemCount":{
-          "shape":"Long",
-          "documentation":"<p>The number of items in the specified table. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p>"
-        },
-        "LocalSecondaryIndexes":{
-          "shape":"LocalSecondaryIndexDescriptionList",
-          "documentation":"<p>Represents one or more local secondary indexes on the table. Each index is scoped to a given hash key value. Tables with one or more local secondary indexes are subject to an item collection size limit, where the amount of data within a given item collection cannot exceed 10 GB. Each element is composed of:</p> <ul> <li> <p><i>IndexName</i> - The name of the local secondary index.</p> </li> <li> <p><i>KeySchema</i> - Specifies the complete index key schema. The attribute names in the key schema must be between 1 and 255 characters (inclusive). The key schema must begin with the same hash key attribute as the table.</p> </li> <li> <p><i>Projection</i> - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of:</p> <ul> <li> <p><i>ProjectionType</i> - One of the following:</p> <ul> <li> <p><code>KEYS_ONLY</code> - Only the index and primary keys are projected into the index.</p> </li> <li> <p><code>INCLUDE</code> - Only the specified table attributes are projected into the index. The list of projected attributes are in <i>NonKeyAttributes</i>.</p> </li> <li> <p><code>ALL</code> - All of the table attributes are projected into the index.</p> </li> </ul> </li> <li> <p><i>NonKeyAttributes</i> - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes specified in <i>NonKeyAttributes</i>, summed across all of the secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total.</p> </li> </ul> </li> <li> <p><i>IndexSizeBytes</i> - Represents the total size of the index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.</p> </li> <li> <p><i>ItemCount</i> - Represents the number of items in the index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.</p> </li> </ul> <p>If the table is in the <code>DELETING</code> state, no information about indexes will be returned.</p>"
-        },
-        "GlobalSecondaryIndexes":{
-          "shape":"GlobalSecondaryIndexDescriptionList",
-          "documentation":"<p>The global secondary indexes, if any, on the table. Each index is scoped to a given hash key value. Each element is composed of:</p> <ul> <li> <p><i>IndexName</i> - The name of the global secondary index.</p> </li> <li> <p><i>IndexSizeBytes</i> - The total size of the global secondary index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p> </li> <li> <p><i>IndexStatus</i> - The current status of the global secondary index:</p> <ul> <li> <p><i>CREATING</i> - The index is being created.</p> </li> <li> <p><i>UPDATING</i> - The index is being updated.</p> </li> <li> <p><i>DELETING</i> - The index is being deleted.</p> </li> <li> <p><i>ACTIVE</i> - The index is ready for use.</p> </li> </ul> </li> <li> <p><i>ItemCount</i> - The number of items in the global secondary index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. </p> </li> <li> <p><i>KeySchema</i> - Specifies the complete index key schema. The attribute names in the key schema must be between 1 and 255 characters (inclusive). The key schema must begin with the same hash key attribute as the table.</p> </li> <li> <p><i>Projection</i> - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of:</p> <ul> <li> <p><i>ProjectionType</i> - One of the following:</p> <ul> <li> <p><code>KEYS_ONLY</code> - Only the index and primary keys are projected into the index.</p> </li> <li> <p><code>INCLUDE</code> - Only the specified table attributes are projected into the index. The list of projected attributes are in <i>NonKeyAttributes</i>.</p> </li> <li> <p><code>ALL</code> - All of the table attributes are projected into the index.</p> </li> </ul> </li> <li> <p><i>NonKeyAttributes</i> - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes specified in <i>NonKeyAttributes</i>, summed across all of the secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total.</p> </li> </ul> </li> <li> <p><i>ProvisionedThroughput</i> - The provisioned throughput settings for the global secondary index, consisting of read and write capacity units, along with data about increases and decreases. </p> </li> </ul> <p>If the table is in the <code>DELETING</code> state, no information about indexes will be returned.</p>"
-        }
-      },
-      "documentation":"<p>Represents the properties of a table.</p>"
-    },
-    "TableName":{
-      "type":"string",
-      "min":3,
-      "max":255,
-      "pattern":"[a-zA-Z0-9_.-]+"
-    },
-    "TableNameList":{
-      "type":"list",
-      "member":{"shape":"TableName"}
-    },
-    "TableStatus":{
-      "type":"string",
-      "enum":[
-        "CREATING",
-        "UPDATING",
-        "DELETING",
-        "ACTIVE"
-      ]
-    },
-    "UpdateGlobalSecondaryIndexAction":{
-      "type":"structure",
-      "required":[
-        "IndexName",
-        "ProvisionedThroughput"
-      ],
-      "members":{
-        "IndexName":{
-          "shape":"IndexName",
-          "documentation":"<p>The name of the global secondary index to be updated.</p>"
-        },
-        "ProvisionedThroughput":{"shape":"ProvisionedThroughput"}
-      },
-      "documentation":"<p>Represents the new provisioned throughput settings to be applied to a global secondary index.</p>"
-    },
-    "UpdateItemInput":{
-      "type":"structure",
-      "required":[
-        "TableName",
-        "Key"
-      ],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table containing the item to update. </p>"
-        },
-        "Key":{
-          "shape":"Key",
-          "documentation":"<p>The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute.</p> <p>For the primary key, you must provide <i>all</i> of the attributes. For example, with a hash type primary key, you only need to specify the hash attribute. For a hash-and-range type primary key, you must specify <i>both</i> the hash attribute and the range attribute.</p>"
-        },
-        "AttributeUpdates":{
-          "shape":"AttributeUpdates",
-          "documentation":"<p>The names of attributes to be modified, the action to perform on each, and the new value for each. If you are updating an attribute that is an index key attribute for any indexes on that table, the attribute type must match the index key type defined in the <i>AttributesDefinition</i> of the table description. You can use <i>UpdateItem</i> to update any non-key attributes.</p> <p>Attribute values cannot be null. String and binary type attributes must have lengths greater than zero. Set type attributes must not be empty. Requests with empty values will be rejected with a <i>ValidationException</i>.</p> <p>Each <i>AttributeUpdates</i> element consists of an attribute name to modify, along with the following:</p> <ul> <li> <p><i>Value</i> - The new value, if applicable, for this attribute.</p> </li> <li> <p><i>Action</i> - Specifies how to perform the update. Valid values for <i>Action</i> are <code>PUT</code>, <code>DELETE</code>, and <code>ADD</code>. The behavior depends on whether the specified primary key already exists in the table.</p> <p> <b>If an item with the specified <i>Key</i> is found in the table:</b> </p> <ul> <li> <p><code>PUT</code> - Adds the specified attribute to the item. If the attribute already exists, it is replaced by the new value. </p> </li> <li> <p><code>DELETE</code> - If no value is specified, the attribute and its value are removed from the item. The data type of the specified value must match the existing value's data type.</p> <p>If a <i>set</i> of values is specified, then those values are subtracted from the old set. For example, if the attribute value was the set <code>[a,b,c]</code> and the <i>DELETE</i> action specified <code>[a,c]</code>, then the final attribute value would be <code>[b]</code>. Specifying an empty set is an error.</p> </li> <li> <p><code>ADD</code> - If the attribute does not already exist, then the attribute and its values are added to the item. If the attribute does exist, then the behavior of <code>ADD</code> depends on the data type of the attribute:</p> <ul> <li> <p>If the existing attribute is a number, and if <i>Value</i> is also a number, then the <i>Value</i> is mathematically added to the existing attribute. If <i>Value</i> is a negative number, then it is subtracted from the existing attribute.</p> </li> <li> <p>If the existing data type is a set, and if the <i>Value</i> is also a set, then the <i>Value</i> is added to the existing set. (This is a <i>set</i> operation, not mathematical addition.) For example, if the attribute value was the set <code>[1,2]</code>, and the <code>ADD</code> action specified <code>[3]</code>, then the final attribute value would be <code>[1,2,3]</code>. An error occurs if an Add action is specified for a set attribute and the attribute type specified does not match the existing set type. </p> <p>Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the <i>Value</i> must also be a set of strings. The same holds true for number sets and binary sets.</p> </li> </ul> <p>This action is only valid for an existing attribute whose data type is number or is a set. Do not use <code>ADD</code> for any other data types.</p> </li> </ul> <p> <b>If no item with the specified <i>Key</i> is found:</b> </p> <ul> <li> <p><code>PUT</code> - DynamoDB creates a new item with the specified primary key, and then adds the attribute. </p> </li> <li> <p><code>DELETE</code> - Nothing happens; there is no attribute to delete.</p> </li> <li> <p><code>ADD</code> - DynamoDB creates an item with the supplied primary key and number (or set of numbers) for the attribute value. The only data types allowed are number and number set; no other data types can be specified.</p> </li> </ul> </li> </ul> <p>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.</p>"
-        },
-        "Expected":{
-          "shape":"ExpectedAttributeMap",
-          "documentation":"<p>A map of attribute/condition pairs. This is the conditional block for the <i>UpdateItem</i> operation.</p> <p>Each element of <i>Expected</i> consists of an attribute name, a comparison operator, and one or more values. DynamoDB compares the attribute with the value(s) you supplied, using the comparison operator. For each <i>Expected</i> element, the result of the evaluation is either true or false.</p> <p>If you specify more than one element in the <i>Expected</i> map, then by default all of the conditions must evaluate to true. In other words, the conditions are ANDed together. (You can use the <i>ConditionalOperator</i> parameter to OR the conditions instead. If you do this, then at least one of the conditions must evaluate to true, rather than all of them.)</p> <p>If the <i>Expected</i> map evaluates to true, then the conditional operation succeeds; otherwise, it fails.</p> <p>Each item in <i>Expected</i> represents an attribute name for DynamoDB to check, along with an <i>AttributeValueList</i> and a <i>ComparisonOperator</i>:</p> <ul> <li> <p><i>AttributeValueList</i> - One or more values to evaluate against the supplied attribute. The number of values in the list depends on the <i>ComparisonOperator</i> being used.</p> <p>For type Number, value comparisons are numeric.</p> <p>String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, <code>a</code> is greater than <code>A</code>, and <code>aa</code> is greater than <code>B</code>. For a list of code values, see <a href=\"http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters\" >http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a>.</p> <p>For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values, for example when evaluating query expressions.</p> </li> <li> <p><i>ComparisonOperator</i> - A comparator for evaluating attributes in the <i>AttributeValueList</i>. When performing the comparison, DynamoDB uses strongly consistent reads.</p> <p>The following comparison operators are available:</p> <p><code>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</code></p> <p>The following are descriptions of each comparison operator.</p> <ul> <li> <p><code>EQ</code> : Equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NE</code> : Not equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not equal <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LE</code> : Less than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>LT</code> : Less than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GE</code> : Greater than or equal. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>GT</code> : Greater than. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not equal <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code>.</p> <p/> </li> <li> <p><code>NOT_NULL</code> : The attribute exists. </p> </li> <li> <p><code>NULL</code> : The attribute does not exist. </p> </li> <li> <p><code>CONTAINS</code> : checks for a subsequence, or value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for a substring match. If the target attribute of the comparison is Binary, then the operation looks for a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for a member of the set (not as a substring).</p> </li> <li> <p><code>NOT_CONTAINS</code> : checks for absence of a subsequence, or absence of a value in a set.</p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String, Number, or Binary (not a set). If the target attribute of the comparison is a String, then the operation checks for the absence of a substring match. If the target attribute of the comparison is Binary, then the operation checks for the absence of a subsequence of the target that matches the input. If the target attribute of the comparison is a set (\"SS\", \"NS\", or \"BS\"), then the operation checks for the absence of a member of the set (not as a substring).</p></li> <li> <p><code>BEGINS_WITH</code> : checks for a prefix. </p> <p><i>AttributeValueList</i> can contain only one <i>AttributeValue</i> of type String or Binary (not a Number or a set). The target attribute of the comparison must be a String or Binary (not a Number or a set).</p> <p/> </li> <li> <p><code>IN</code> : checks for exact matches.</p> <p><i>AttributeValueList</i> can contain more than one <i>AttributeValue</i> of type String, Number, or Binary (not a set). The target attribute of the comparison must be of the same type and exact value to match. A String never matches a String set.</p> </li> <li> <p><code>BETWEEN</code> : Greater than or equal to the first value, and less than or equal to the second value. </p> <p><i>AttributeValueList</i> must contain two <i>AttributeValue</i> elements of the same type, either String, Number, or Binary (not a set). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an <i>AttributeValue</i> of a different type than the one specified in the request, the value does not match. For example, <code>{\"S\":\"6\"}</code> does not compare to <code>{\"N\":\"6\"}</code>. Also, <code>{\"N\":\"6\"}</code> does not compare to <code>{\"NS\":[\"6\", \"2\", \"1\"]}</code></p> </li> </ul> </li> </ul> <p>For usage examples of <i>AttributeValueList</i> and <i>ComparisonOperator</i>, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html#ConditionalExpressions\" >Conditional Expressions</a> in the Amazon DynamoDB Developer Guide.</p>"
-        },
-        "ConditionalOperator":{
-          "shape":"ConditionalOperator",
-          "documentation":"<p>A logical operator to apply to the conditions in the <i>Expected</i> map:</p> <ul> <li><p><code>AND</code> - If <i>all</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> <li><p><code>OR</code> - If <i>at least one</i> of the conditions evaluate to true, then the entire map evaluates to true.</p></li> </ul> <p>If you omit <i>ConditionalOperator</i>, then <code>AND</code> is the default.</p> <p>The operation will succeed only if the entire map evaluates to true.</p>"
-        },
-        "ReturnValues":{
-          "shape":"ReturnValue",
-          "documentation":"<p>Use <i>ReturnValues</i> if you want to get the item attributes as they appeared either before or after they were updated. For <i>UpdateItem</i>, the valid values are:</p> <ul> <li> <p><code>NONE</code> - If <i>ReturnValues</i> is not specified, or if its value is <code>NONE</code>, then nothing is returned. (This is the default for <i>ReturnValues</i>.)</p> </li> <li> <p><code>ALL_OLD</code> - If <i>UpdateItem</i> overwrote an attribute name-value pair, then the content of the old item is returned.</p> </li> <li> <p><code>UPDATED_OLD</code> - The old versions of only the updated attributes are returned.</p> </li> <li> <p><code>ALL_NEW</code> - All of the attributes of the new version of the item are returned.</p> </li> <li> <p><code>UPDATED_NEW</code> - The new versions of only the updated attributes are returned.</p> </li> </ul>"
-        },
-        "ReturnConsumedCapacity":{"shape":"ReturnConsumedCapacity"},
-        "ReturnItemCollectionMetrics":{
-          "shape":"ReturnItemCollectionMetrics",
-          "documentation":"<p>If set to <code>SIZE</code>, statistics about item collections, if any, that were modified during the operation are returned in the response. If set to <code>NONE</code> (the default), no statistics are returned.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of an <i>UpdateItem</i> operation.</p>"
-    },
-    "UpdateItemOutput":{
-      "type":"structure",
-      "members":{
-        "Attributes":{
-          "shape":"AttributeMap",
-          "documentation":"<p>A map of attribute values as they appeared before the <i>UpdateItem</i> operation, but only if <i>ReturnValues</i> was specified as something other than <code>NONE</code> in the request. Each element represents one attribute.</p>"
-        },
-        "ConsumedCapacity":{"shape":"ConsumedCapacity"},
-        "ItemCollectionMetrics":{"shape":"ItemCollectionMetrics"}
-      },
-      "documentation":"<p>Represents the output of an <i>UpdateItem</i> operation.</p>"
-    },
-    "UpdateTableInput":{
-      "type":"structure",
-      "required":["TableName"],
-      "members":{
-        "TableName":{
-          "shape":"TableName",
-          "documentation":"<p>The name of the table to be updated.</p>"
-        },
-        "ProvisionedThroughput":{"shape":"ProvisionedThroughput"},
-        "GlobalSecondaryIndexUpdates":{
-          "shape":"GlobalSecondaryIndexUpdateList",
-          "documentation":"<p>An array of one or more global secondary indexes on the table, together with provisioned throughput settings for each index.</p>"
-        }
-      },
-      "documentation":"<p>Represents the input of an <i>UpdateTable</i> operation.</p>"
-    },
-    "UpdateTableOutput":{
-      "type":"structure",
-      "members":{
-        "TableDescription":{"shape":"TableDescription"}
-      },
-      "documentation":"<p>Represents the output of an <i>UpdateTable</i> operation.</p>"
-    },
-    "WriteRequest":{
-      "type":"structure",
-      "members":{
-        "PutRequest":{
-          "shape":"PutRequest",
-          "documentation":"<p>A request to perform a <i>PutItem</i> operation.</p>"
-        },
-        "DeleteRequest":{
-          "shape":"DeleteRequest",
-          "documentation":"<p>A request to perform a <i>DeleteItem</i> operation.</p>"
-        }
-      },
-      "documentation":"<p>Represents an operation to perform - either <i>DeleteItem</i> or <i>PutItem</i>. You can only specify one of these operations, not both, in a single <i>WriteRequest</i>. If you do need to perform both of these operations, you will need to specify two separate <i>WriteRequest</i> objects.</p>"
-    },
-    "WriteRequests":{
-      "type":"list",
-      "member":{"shape":"WriteRequest"},
-      "min":1,
-      "max":25
-    }
-  }
-}