TrueCloudLab/rclone
16
0
Fork 4
Code Issues 1 Pull requests Projects Releases 4 Packages Wiki Activity Actions

vendor: update all dependencies

Browse source 
* Update all dependencies
  * Remove all `[[constraint]]` from Gopkg.toml
  * Add in the minimum number of `[[override]]` to build
  * Remove go get of github.com/inconshreveable/mousetrap as it is vendored
  * Update docs with new policy on constraints
This commit is contained in:
Nick Craig-Wood 2018-05-02 17:09:45 +01:00
parent 21383877df
commit 6427029c4e
4902 changed files with 1443417 additions and 227283 deletions
Download patch file Download diff file Expand all files Collapse all files

259
vendor/github.com/aws/aws-sdk-go/models/apis/dynamodb/2012-08-10/api-2.json generated vendored
View file

@ -173,6 +173,19 @@
{"shape":"GlobalTableNotFoundException"}
]
},
"DescribeGlobalTableSettings":{
"name":"DescribeGlobalTableSettings",
"http":{
"method":"POST",
"requestUri":"/"
},
"input":{"shape":"DescribeGlobalTableSettingsInput"},
"output":{"shape":"DescribeGlobalTableSettingsOutput"},
"errors":[
{"shape":"GlobalTableNotFoundException"},
{"shape":"InternalServerError"}
]
},
"DescribeLimits":{
"name":"DescribeLimits",
"http":{
@ -321,6 +334,24 @@
{"shape":"InternalServerError"}
]
},
"RestoreTableToPointInTime":{
"name":"RestoreTableToPointInTime",
"http":{
"method":"POST",
"requestUri":"/"
},
"input":{"shape":"RestoreTableToPointInTimeInput"},
"output":{"shape":"RestoreTableToPointInTimeOutput"},
"errors":[
{"shape":"TableAlreadyExistsException"},
{"shape":"TableNotFoundException"},
{"shape":"TableInUseException"},
{"shape":"LimitExceededException"},
{"shape":"InvalidRestoreTimeException"},
{"shape":"PointInTimeRecoveryUnavailableException"},
{"shape":"InternalServerError"}
]
},
"Scan":{
"name":"Scan",
"http":{
@ -363,6 +394,20 @@
{"shape":"ResourceInUseException"}
]
},
"UpdateContinuousBackups":{
"name":"UpdateContinuousBackups",
"http":{
"method":"POST",
"requestUri":"/"
},
"input":{"shape":"UpdateContinuousBackupsInput"},
"output":{"shape":"UpdateContinuousBackupsOutput"},
"errors":[
{"shape":"TableNotFoundException"},
{"shape":"ContinuousBackupsUnavailableException"},
{"shape":"InternalServerError"}
]
},
"UpdateGlobalTable":{
"name":"UpdateGlobalTable",
"http":{
@ -379,6 +424,23 @@
{"shape":"TableNotFoundException"}
]
},
"UpdateGlobalTableSettings":{
"name":"UpdateGlobalTableSettings",
"http":{
"method":"POST",
"requestUri":"/"
},
"input":{"shape":"UpdateGlobalTableSettingsInput"},
"output":{"shape":"UpdateGlobalTableSettingsOutput"},
"errors":[
{"shape":"GlobalTableNotFoundException"},
{"shape":"ReplicaNotFoundException"},
{"shape":"IndexNotFoundException"},
{"shape":"LimitExceededException"},
{"shape":"ResourceInUseException"},
{"shape":"InternalServerError"}
]
},
"UpdateItem":{
"name":"UpdateItem",
"http":{
@ -706,7 +768,8 @@
"type":"structure",
"required":["ContinuousBackupsStatus"],
"members":{
"ContinuousBackupsStatus":{"shape":"ContinuousBackupsStatus"}
"ContinuousBackupsStatus":{"shape":"ContinuousBackupsStatus"},
"PointInTimeRecoveryDescription":{"shape":"PointInTimeRecoveryDescription"}
}
},
"ContinuousBackupsStatus":{
@ -918,6 +981,20 @@
"GlobalTableDescription":{"shape":"GlobalTableDescription"}
}
},
"DescribeGlobalTableSettingsInput":{
"type":"structure",
"required":["GlobalTableName"],
"members":{
"GlobalTableName":{"shape":"TableName"}
}
},
"DescribeGlobalTableSettingsOutput":{
"type":"structure",
"members":{
"GlobalTableName":{"shape":"TableName"},
"ReplicaSettings":{"shape":"ReplicaSettingsDescriptionList"}
}
},
"DescribeLimitsInput":{
"type":"structure",
"members":{
@ -1100,6 +1177,20 @@
"GlobalTableName":{"shape":"TableName"}
}
},
"GlobalTableGlobalSecondaryIndexSettingsUpdate":{
"type":"structure",
"required":["IndexName"],
"members":{
"IndexName":{"shape":"IndexName"},
"ProvisionedWriteCapacityUnits":{"shape":"PositiveLongObject"}
}
},
"GlobalTableGlobalSecondaryIndexSettingsUpdateList":{
"type":"list",
"member":{"shape":"GlobalTableGlobalSecondaryIndexSettingsUpdate"},
"max":20,
"min":1
},
"GlobalTableList":{
"type":"list",
"member":{"shape":"GlobalTable"}
@ -1126,6 +1217,13 @@
"min":3,
"pattern":"[a-zA-Z0-9_.-]+"
},
"IndexNotFoundException":{
"type":"structure",
"members":{
"message":{"shape":"ErrorMessage"}
},
"exception":true
},
"IndexStatus":{
"type":"string",
"enum":[
@ -1144,6 +1242,13 @@
"exception":true,
"fault":true
},
"InvalidRestoreTimeException":{
"type":"structure",
"members":{
"message":{"shape":"ErrorMessage"}
},
"exception":true
},
"ItemCollectionKeyAttributeMap":{
"type":"map",
"key":{"shape":"AttributeName"},
@ -1387,6 +1492,35 @@
"type":"list",
"member":{"shape":"NumberAttributeValue"}
},
"PointInTimeRecoveryDescription":{
"type":"structure",
"members":{
"PointInTimeRecoveryStatus":{"shape":"PointInTimeRecoveryStatus"},
"EarliestRestorableDateTime":{"shape":"Date"},
"LatestRestorableDateTime":{"shape":"Date"}
}
},
"PointInTimeRecoverySpecification":{
"type":"structure",
"required":["PointInTimeRecoveryEnabled"],
"members":{
"PointInTimeRecoveryEnabled":{"shape":"BooleanObject"}
}
},
"PointInTimeRecoveryStatus":{
"type":"string",
"enum":[
"ENABLED",
"DISABLED"
]
},
"PointInTimeRecoveryUnavailableException":{
"type":"structure",
"members":{
"message":{"shape":"ErrorMessage"}
},
"exception":true
},
"PositiveIntegerObject":{
"type":"integer",
"min":1
@ -1535,6 +1669,34 @@
"type":"list",
"member":{"shape":"ReplicaDescription"}
},
"ReplicaGlobalSecondaryIndexSettingsDescription":{
"type":"structure",
"required":["IndexName"],
"members":{
"IndexName":{"shape":"IndexName"},
"IndexStatus":{"shape":"IndexStatus"},
"ProvisionedReadCapacityUnits":{"shape":"PositiveLongObject"},
"ProvisionedWriteCapacityUnits":{"shape":"PositiveLongObject"}
}
},
"ReplicaGlobalSecondaryIndexSettingsDescriptionList":{
"type":"list",
"member":{"shape":"ReplicaGlobalSecondaryIndexSettingsDescription"}
},
"ReplicaGlobalSecondaryIndexSettingsUpdate":{
"type":"structure",
"required":["IndexName"],
"members":{
"IndexName":{"shape":"IndexName"},
"ProvisionedReadCapacityUnits":{"shape":"PositiveLongObject"}
}
},
"ReplicaGlobalSecondaryIndexSettingsUpdateList":{
"type":"list",
"member":{"shape":"ReplicaGlobalSecondaryIndexSettingsUpdate"},
"max":20,
"min":1
},
"ReplicaList":{
"type":"list",
"member":{"shape":"Replica"}
@ -1546,6 +1708,45 @@
},
"exception":true
},
"ReplicaSettingsDescription":{
"type":"structure",
"required":["RegionName"],
"members":{
"RegionName":{"shape":"RegionName"},
"ReplicaStatus":{"shape":"ReplicaStatus"},
"ReplicaProvisionedReadCapacityUnits":{"shape":"PositiveLongObject"},
"ReplicaProvisionedWriteCapacityUnits":{"shape":"PositiveLongObject"},
"ReplicaGlobalSecondaryIndexSettings":{"shape":"ReplicaGlobalSecondaryIndexSettingsDescriptionList"}
}
},
"ReplicaSettingsDescriptionList":{
"type":"list",
"member":{"shape":"ReplicaSettingsDescription"}
},
"ReplicaSettingsUpdate":{
"type":"structure",
"required":["RegionName"],
"members":{
"RegionName":{"shape":"RegionName"},
"ReplicaProvisionedReadCapacityUnits":{"shape":"PositiveLongObject"},
"ReplicaGlobalSecondaryIndexSettingsUpdate":{"shape":"ReplicaGlobalSecondaryIndexSettingsUpdateList"}
}
},
"ReplicaSettingsUpdateList":{
"type":"list",
"member":{"shape":"ReplicaSettingsUpdate"},
"max":50,
"min":1
},
"ReplicaStatus":{
"type":"string",
"enum":[
"CREATING",
"UPDATING",
"DELETING",
"ACTIVE"
]
},
"ReplicaUpdate":{
"type":"structure",
"members":{
@ -1576,7 +1777,6 @@
},
"exception":true
},
"RestoreDateTime":{"type":"timestamp"},
"RestoreInProgress":{"type":"boolean"},
"RestoreSummary":{
"type":"structure",
@ -1587,7 +1787,7 @@
"members":{
"SourceBackupArn":{"shape":"BackupArn"},
"SourceTableArn":{"shape":"TableArn"},
"RestoreDateTime":{"shape":"RestoreDateTime"},
"RestoreDateTime":{"shape":"Date"},
"RestoreInProgress":{"shape":"RestoreInProgress"}
}
},
@ -1608,6 +1808,25 @@
"TableDescription":{"shape":"TableDescription"}
}
},
"RestoreTableToPointInTimeInput":{
"type":"structure",
"required":[
"SourceTableName",
"TargetTableName"
],
"members":{
"SourceTableName":{"shape":"TableName"},
"TargetTableName":{"shape":"TableName"},
"UseLatestRestorableTime":{"shape":"BooleanObject"},
"RestoreDateTime":{"shape":"Date"}
}
},
"RestoreTableToPointInTimeOutput":{
"type":"structure",
"members":{
"TableDescription":{"shape":"TableDescription"}
}
},
"ReturnConsumedCapacity":{
"type":"string",
"enum":[
@ -1932,6 +2151,23 @@
"TagKeys":{"shape":"TagKeyList"}
}
},
"UpdateContinuousBackupsInput":{
"type":"structure",
"required":[
"TableName",
"PointInTimeRecoverySpecification"
],
"members":{
"TableName":{"shape":"TableName"},
"PointInTimeRecoverySpecification":{"shape":"PointInTimeRecoverySpecification"}
}
},
"UpdateContinuousBackupsOutput":{
"type":"structure",
"members":{
"ContinuousBackupsDescription":{"shape":"ContinuousBackupsDescription"}
}
},
"UpdateExpression":{"type":"string"},
"UpdateGlobalSecondaryIndexAction":{
"type":"structure",
@ -1961,6 +2197,23 @@
"GlobalTableDescription":{"shape":"GlobalTableDescription"}
}
},
"UpdateGlobalTableSettingsInput":{
"type":"structure",
"required":["GlobalTableName"],
"members":{
"GlobalTableName":{"shape":"TableName"},
"GlobalTableProvisionedWriteCapacityUnits":{"shape":"PositiveLongObject"},
"GlobalTableGlobalSecondaryIndexSettingsUpdate":{"shape":"GlobalTableGlobalSecondaryIndexSettingsUpdateList"},
"ReplicaSettingsUpdate":{"shape":"ReplicaSettingsUpdateList"}
}
},
"UpdateGlobalTableSettingsOutput":{
"type":"structure",
"members":{
"GlobalTableName":{"shape":"TableName"},
"ReplicaSettings":{"shape":"ReplicaSettingsDescriptionList"}
}
},
"UpdateItemInput":{
"type":"structure",
"required":[

216
vendor/github.com/aws/aws-sdk-go/models/apis/dynamodb/2012-08-10/docs-2.json generated vendored
View file

@ -3,16 +3,17 @@
"service": "<fullname>Amazon DynamoDB</fullname> <p>Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. DynamoDB lets you offload the administrative burdens of operating and scaling a distributed database, so that you don't have to worry about hardware provisioning, setup and configuration, replication, software patching, or cluster scaling.</p> <p>With DynamoDB, you can create database tables that can store and retrieve any amount of data, and serve any level of request traffic. You can scale up or scale down your tables' throughput capacity without downtime or performance degradation, and use the AWS Management Console to monitor resource utilization and performance metrics.</p> <p>DynamoDB automatically spreads the data and traffic for your tables over a sufficient number of servers to handle your throughput and storage requirements, while maintaining consistent and fast performance. All of your data is stored on solid state disks (SSDs) and automatically replicated across multiple Availability Zones in an AWS region, providing built-in high availability and data durability. </p>",
"operations": {
"BatchGetItem": "<p>The <code>BatchGetItem</code> operation returns the attributes of one or more items from one or more tables. You identify requested items by primary key.</p> <p>A single operation can retrieve up to 16 MB of data, which can contain as many as 100 items. <code>BatchGetItem</code> 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 <code>UnprocessedKeys</code>. You can use this value to retry the operation starting with the next item to get.</p> <important> <p>If you request more than 100 items <code>BatchGetItem</code> will return a <code>ValidationException</code> with the message \"Too many items requested for the BatchGetItem call\".</p> </important> <p>For example, if you ask to retrieve 100 items, but each individual item is 300 KB in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also returns an appropriate <code>UnprocessedKeys</code> value so you can get the next page of results. If desired, your application can include its own logic to assemble the pages of results into one data set.</p> <p>If <i>none</i> of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then <code>BatchGetItem</code> will return a <code>ProvisionedThroughputExceededException</code>. If <i>at least one</i> of the items is successfully processed, then <code>BatchGetItem</code> completes successfully, while returning the keys of the unread items in <code>UnprocessedKeys</code>.</p> <important> <p>If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, <i>we strongly recommend that you use an exponential backoff algorithm</i>. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations\">Batch Operations and Error Handling</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> </important> <p>By default, <code>BatchGetItem</code> performs eventually consistent reads on every table in the request. If you want strongly consistent reads instead, you can set <code>ConsistentRead</code> to <code>true</code> for any or all tables.</p> <p>In order to minimize response latency, <code>BatchGetItem</code> retrieves items in parallel.</p> <p>When designing your application, keep in mind that DynamoDB does not return items in any particular order. To help parse the response by item, include the primary key values for the items in your request in the <code>ProjectionExpression</code> parameter.</p> <p>If a requested item does not exist, it is not returned in the result. Requests for nonexistent items consume the minimum read capacity units according to the type of read. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#CapacityUnitCalculations\">Capacity Units Calculations</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
"BatchWriteItem": "<p>The <code>BatchWriteItem</code> operation puts or deletes multiple items in one or more tables. A single call to <code>BatchWriteItem</code> can write up to 16 MB of data, which can comprise as many as 25 put or delete requests. Individual items to be written can be as large as 400 KB.</p> <note> <p> <code>BatchWriteItem</code> cannot update items. To update items, use the <code>UpdateItem</code> action.</p> </note> <p>The individual <code>PutItem</code> and <code>DeleteItem</code> operations specified in <code>BatchWriteItem</code> are atomic; however <code>BatchWriteItem</code> as a whole is not. If any requested operations fail because the table's provisioned throughput is exceeded or an internal processing failure occurs, the failed operations are returned in the <code>UnprocessedItems</code> response parameter. You can investigate and optionally resend the requests. Typically, you would call <code>BatchWriteItem</code> in a loop. Each iteration would check for unprocessed items and submit a new <code>BatchWriteItem</code> request with those unprocessed items until all items have been processed.</p> <p>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 <code>BatchWriteItem</code> will return a <code>ProvisionedThroughputExceededException</code>.</p> <important> <p>If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, <i>we strongly recommend that you use an exponential backoff algorithm</i>. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations\">Batch Operations and Error Handling</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> </important> <p>With <code>BatchWriteItem</code>, 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, <code>BatchWriteItem</code> does not behave in the same way as individual <code>PutItem</code> and <code>DeleteItem</code> calls would. For example, you cannot specify conditions on individual put and delete requests, and <code>BatchWriteItem</code> does not return deleted items in the response.</p> <p>If you use a programming language that supports concurrency, you can use threads to write items in parallel. Your application must include the necessary logic to manage the threads. With languages that don't support threading, you must update or delete the specified items one at a time. In both situations, <code>BatchWriteItem</code> performs the specified put and delete operations in parallel, giving you the power of the thread pool approach without having to introduce complexity into your application.</p> <p>Parallel processing reduces latency, but each specified put and delete request consumes the same number of write capacity units whether it is processed in parallel or not. Delete operations on nonexistent items consume one write capacity unit.</p> <p>If one or more of the following is true, DynamoDB rejects the entire batch write operation:</p> <ul> <li> <p>One or more tables specified in the <code>BatchWriteItem</code> request does not exist.</p> </li> <li> <p>Primary key attributes specified on an item in the request do not match those in the corresponding table's primary key schema.</p> </li> <li> <p>You try to perform multiple operations on the same item in the same <code>BatchWriteItem</code> request. For example, you cannot put and delete the same item in the same <code>BatchWriteItem</code> request. </p> </li> <li> <p>There are more than 25 requests in the batch.</p> </li> <li> <p>Any individual item in a batch exceeds 400 KB.</p> </li> <li> <p>The total request size exceeds 16 MB.</p> </li> </ul>",
"BatchWriteItem": "<p>The <code>BatchWriteItem</code> operation puts or deletes multiple items in one or more tables. A single call to <code>BatchWriteItem</code> can write up to 16 MB of data, which can comprise as many as 25 put or delete requests. Individual items to be written can be as large as 400 KB.</p> <note> <p> <code>BatchWriteItem</code> cannot update items. To update items, use the <code>UpdateItem</code> action.</p> </note> <p>The individual <code>PutItem</code> and <code>DeleteItem</code> operations specified in <code>BatchWriteItem</code> are atomic; however <code>BatchWriteItem</code> as a whole is not. If any requested operations fail because the table's provisioned throughput is exceeded or an internal processing failure occurs, the failed operations are returned in the <code>UnprocessedItems</code> response parameter. You can investigate and optionally resend the requests. Typically, you would call <code>BatchWriteItem</code> in a loop. Each iteration would check for unprocessed items and submit a new <code>BatchWriteItem</code> request with those unprocessed items until all items have been processed.</p> <p>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 <code>BatchWriteItem</code> will return a <code>ProvisionedThroughputExceededException</code>.</p> <important> <p>If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, <i>we strongly recommend that you use an exponential backoff algorithm</i>. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations\">Batch Operations and Error Handling</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> </important> <p>With <code>BatchWriteItem</code>, 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, <code>BatchWriteItem</code> does not behave in the same way as individual <code>PutItem</code> and <code>DeleteItem</code> calls would. For example, you cannot specify conditions on individual put and delete requests, and <code>BatchWriteItem</code> does not return deleted items in the response.</p> <p>If you use a programming language that supports concurrency, you can use threads to write items in parallel. Your application must include the necessary logic to manage the threads. With languages that don't support threading, you must update or delete the specified items one at a time. In both situations, <code>BatchWriteItem</code> performs the specified put and delete operations in parallel, giving you the power of the thread pool approach without having to introduce complexity into your application.</p> <p>Parallel processing reduces latency, but each specified put and delete request consumes the same number of write capacity units whether it is processed in parallel or not. Delete operations on nonexistent items consume one write capacity unit.</p> <p>If one or more of the following is true, DynamoDB rejects the entire batch write operation:</p> <ul> <li> <p>One or more tables specified in the <code>BatchWriteItem</code> request does not exist.</p> </li> <li> <p>Primary key attributes specified on an item in the request do not match those in the corresponding table's primary key schema.</p> </li> <li> <p>You try to perform multiple operations on the same item in the same <code>BatchWriteItem</code> request. For example, you cannot put and delete the same item in the same <code>BatchWriteItem</code> request. </p> </li> <li> <p> Your request contains at least two items with identical hash and range keys (which essentially is two put operations). </p> </li> <li> <p>There are more than 25 requests in the batch.</p> </li> <li> <p>Any individual item in a batch exceeds 400 KB.</p> </li> <li> <p>The total request size exceeds 16 MB.</p> </li> </ul>",
"CreateBackup": "<p>Creates a backup for an existing table.</p> <p> Each time you create an On-Demand Backup, the entire table data is backed up. There is no limit to the number of on-demand backups that can be taken. </p> <p> When you create an On-Demand Backup, a time marker of the request is cataloged, and the backup is created asynchronously, by applying all changes until the time of the request to the last full table snapshot. Backup requests are processed instantaneously and become available for restore within minutes. </p> <p>You can call <code>CreateBackup</code> at a maximum rate of 50 times per second.</p> <p>All backups in DynamoDB work without consuming any provisioned throughput on the table.</p> <p> If you submit a backup request on 2018-12-14 at 14:25:00, the backup is guaranteed to contain all data committed to the table up to 14:24:00, and data committed after 14:26:00 will not be. The backup may or may not contain data modifications made between 14:24:00 and 14:26:00. On-Demand Backup does not support causal consistency. </p> <p> Along with data, the following are also included on the backups: </p> <ul> <li> <p>Global secondary indexes (GSIs)</p> </li> <li> <p>Local secondary indexes (LSIs)</p> </li> <li> <p>Streams</p> </li> <li> <p>Provisioned read and write capacity</p> </li> </ul>",
"CreateGlobalTable": "<p>Creates a global table from an existing table. A global table creates a replication relationship between two or more DynamoDB tables with the same table name in the provided regions. </p> <p> Tables can only be added as the replicas of a global table group under the following conditions: </p> <ul> <li> <p> The tables must have the same name. </p> </li> <li> <p> The tables must contain no items. </p> </li> <li> <p> The tables must have the same hash key and sort key (if present). </p> </li> <li> <p> The tables must have DynamoDB Streams enabled (NEW_AND_OLD_IMAGES). </p> </li> </ul>",
"CreateGlobalTable": "<p>Creates a global table from an existing table. A global table creates a replication relationship between two or more DynamoDB tables with the same table name in the provided regions. </p> <p> Tables can only be added as the replicas of a global table group under the following conditions: </p> <ul> <li> <p> The tables must have the same name. </p> </li> <li> <p> The tables must contain no items. </p> </li> <li> <p> The tables must have the same hash key and sort key (if present). </p> </li> <li> <p> The tables must have DynamoDB Streams enabled (NEW_AND_OLD_IMAGES). </p> </li> <li> <p> The tables must have same provisioned and maximum write capacity units. </p> </li> </ul> <p> If global secondary indexes are specified, then the following conditions must also be met: </p> <ul> <li> <p> The global secondary indexes must have the same name. </p> </li> <li> <p> The global secondary indexes must have the same hash key and sort key (if present). </p> </li> <li> <p> The global secondary indexes must have the same provisioned and maximum write capacity units. </p> </li> </ul>",
"CreateTable": "<p>The <code>CreateTable</code> operation adds a new table to your account. In an AWS account, table names must be unique within each region. That is, you can have two tables with same name if you create the tables in different regions.</p> <p> <code>CreateTable</code> is an asynchronous operation. Upon receiving a <code>CreateTable</code> request, DynamoDB immediately returns a response with a <code>TableStatus</code> of <code>CREATING</code>. After the table is created, DynamoDB sets the <code>TableStatus</code> to <code>ACTIVE</code>. You can perform read and write operations only on an <code>ACTIVE</code> table. </p> <p>You can optionally define secondary indexes on the new table, as part of the <code>CreateTable</code> operation. If you want to create multiple tables with secondary indexes on them, you must create the tables sequentially. Only one table with secondary indexes can be in the <code>CREATING</code> state at any given time.</p> <p>You can use the <code>DescribeTable</code> action to check the table status.</p>",
"DeleteBackup": "<p>Deletes an existing backup of a table.</p> <p>You can call <code>DeleteBackup</code> at a maximum rate of 10 times per second.</p>",
"DeleteItem": "<p>Deletes a single item in a table by primary key. You can perform a conditional delete operation that deletes the item if it exists, or if it has an expected attribute value.</p> <p>In addition to deleting an item, you can also return the item's attribute values in the same operation, using the <code>ReturnValues</code> parameter.</p> <p>Unless you specify conditions, the <code>DeleteItem</code> is an idempotent operation; running it multiple times on the same item or attribute does <i>not</i> result in an error response.</p> <p>Conditional deletes are useful for deleting items only if specific conditions are met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item is not deleted.</p>",
"DeleteTable": "<p>The <code>DeleteTable</code> operation deletes a table and all of its items. After a <code>DeleteTable</code> 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 <code>ResourceInUseException</code>. If the specified table does not exist, DynamoDB returns a <code>ResourceNotFoundException</code>. If table is already in the <code>DELETING</code> state, no error is returned. </p> <note> <p>DynamoDB might continue to accept data read and write operations, such as <code>GetItem</code> and <code>PutItem</code>, on a table in the <code>DELETING</code> state until the table deletion is complete.</p> </note> <p>When you delete a table, any indexes on that table are also deleted.</p> <p>If you have DynamoDB Streams enabled on the table, then the corresponding stream on that table goes into the <code>DISABLED</code> state, and the stream is automatically deleted after 24 hours.</p> <p>Use the <code>DescribeTable</code> action to check the status of the table. </p>",
"DescribeBackup": "<p>Describes an existing backup of a table.</p> <p>You can call <code>DescribeBackup</code> at a maximum rate of 10 times per second.</p>",
"DescribeContinuousBackups": "<p>Checks the status of the backup restore settings on the specified table. If backups are enabled, <code>ContinuousBackupsStatus</code> will bet set to ENABLED.</p> <p>You can call <code>DescribeContinuousBackups</code> at a maximum rate of 10 times per second.</p>",
"DescribeContinuousBackups": "<p>Checks the status of continuous backups and point in time recovery on the specified table. Continuous backups are <code>ENABLED</code> on all tables at table creation. If point in time recovery is enabled, <code>PointInTimeRecoveryStatus</code> will be set to ENABLED.</p> <p> Once continuous backups and point in time recovery are enabled, you can restore to any point in time within <code>EarliestRestorableDateTime</code> and <code>LatestRestorableDateTime</code>. </p> <p> <code>LatestRestorableDateTime</code> is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days. </p> <p>You can call <code>DescribeContinuousBackups</code> at a maximum rate of 10 times per second.</p>",
"DescribeGlobalTable": "<p>Returns information about the specified global table.</p>",
"DescribeGlobalTableSettings": "<p>Describes region specific settings for a global table.</p>",
"DescribeLimits": "<p>Returns the current provisioned-capacity limits for your AWS account in a region, both for the region as a whole and for any one DynamoDB table that you create there.</p> <p>When you establish an AWS account, the account has initial limits on the maximum read capacity units and write capacity units that you can provision across all of your DynamoDB tables in a given region. Also, there are per-table limits that apply when you create a table there. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html\">Limits</a> page in the <i>Amazon DynamoDB Developer Guide</i>.</p> <p>Although you can increase these limits by filing a case at <a href=\"https://console.aws.amazon.com/support/home#/\">AWS Support Center</a>, obtaining the increase is not instantaneous. The <code>DescribeLimits</code> action lets you write code to compare the capacity you are currently using to those limits imposed by your account so that you have enough time to apply for an increase before you hit a limit.</p> <p>For example, you could use one of the AWS SDKs to do the following:</p> <ol> <li> <p>Call <code>DescribeLimits</code> for a particular region to obtain your current account limits on provisioned capacity there.</p> </li> <li> <p>Create a variable to hold the aggregate read capacity units provisioned for all your tables in that region, and one to hold the aggregate write capacity units. Zero them both.</p> </li> <li> <p>Call <code>ListTables</code> to obtain a list of all your DynamoDB tables.</p> </li> <li> <p>For each table name listed by <code>ListTables</code>, do the following:</p> <ul> <li> <p>Call <code>DescribeTable</code> with the table name.</p> </li> <li> <p>Use the data returned by <code>DescribeTable</code> to add the read capacity units and write capacity units provisioned for the table itself to your variables.</p> </li> <li> <p>If the table has one or more global secondary indexes (GSIs), loop over these GSIs and add their provisioned capacity values to your variables as well.</p> </li> </ul> </li> <li> <p>Report the account limits for that region returned by <code>DescribeLimits</code>, along with the total current provisioned capacity levels you have calculated.</p> </li> </ol> <p>This will let you see whether you are getting close to your account-level limits.</p> <p>The per-table limits apply only when you are creating a new table. They restrict the sum of the provisioned capacity of the new table itself and all its global secondary indexes.</p> <p>For existing tables and their GSIs, DynamoDB will not let you increase provisioned capacity extremely rapidly, but the only upper limit that applies is that the aggregate provisioned capacity over all your tables and GSIs cannot exceed either of the per-account limits.</p> <note> <p> <code>DescribeLimits</code> should only be called periodically. You can expect throttling errors if you call it more than once in a minute.</p> </note> <p>The <code>DescribeLimits</code> Request element has no content.</p>",
"DescribeTable": "<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> <note> <p>If you issue a <code>DescribeTable</code> request immediately after a <code>CreateTable</code> request, DynamoDB might return a <code>ResourceNotFoundException</code>. This is because <code>DescribeTable</code> uses an eventually consistent query, and the metadata for your table might not be available at that moment. Wait for a few seconds, and then try the <code>DescribeTable</code> request again.</p> </note>",
"DescribeTimeToLive": "<p>Gives a description of the Time to Live (TTL) status on the specified table. </p>",
@ -23,11 +24,14 @@
"ListTagsOfResource": "<p>List all tags on an Amazon DynamoDB resource. You can call ListTagsOfResource up to 10 times per second, per account.</p> <p>For an overview on tagging DynamoDB resources, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html\">Tagging for DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
"PutItem": "<p>Creates a new item, or replaces an old item with a new item. If an item that has the same primary key as the new item already exists in the specified table, the new item completely replaces the existing item. You can perform a conditional put operation (add a new item if one with the specified primary key doesn't exist), or replace an existing item if it has certain attribute values. You can return the item's attribute values in the same operation, using the <code>ReturnValues</code> parameter.</p> <important> <p>This topic provides general information about the <code>PutItem</code> API.</p> <p>For information on how to call the <code>PutItem</code> API using the AWS SDK in specific languages, see the following:</p> <ul> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/aws-cli/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS Command Line Interface </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/DotNetSDKV3/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for .NET </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/SdkForCpp/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for C++ </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/SdkForGoV1/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for Go </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/SdkForJava/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for Java </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/AWSJavaScriptSDK/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for JavaScript </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/SdkForPHPV3/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for PHP V3 </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/boto3/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for Python </a> </p> </li> <li> <p> <a href=\"http://docs.aws.amazon.com/goto/SdkForRubyV2/dynamodb-2012-08-10/PutItem\"> PutItem in the AWS SDK for Ruby V2 </a> </p> </li> </ul> </important> <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 <code>ValidationException</code> exception.</p> <note> <p>To prevent a new item from replacing an existing item, use a conditional expression that contains the <code>attribute_not_exists</code> function with the name of the attribute being used as the partition key for the table. Since every record must contain that attribute, the <code>attribute_not_exists</code> function will only succeed if no matching item exists.</p> </note> <p>For more information about <code>PutItem</code>, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html\">Working with Items</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
"Query": "<p>The <code>Query</code> operation finds items based on primary key values. You can query any table or secondary index that has a composite primary key (a partition key and a sort key). </p> <p>Use the <code>KeyConditionExpression</code> parameter to provide a specific value for the partition key. The <code>Query</code> operation will return all of the items from the table or index with that partition key value. You can optionally narrow the scope of the <code>Query</code> operation by specifying a sort key value and a comparison operator in <code>KeyConditionExpression</code>. To further refine the <code>Query</code> results, you can optionally provide a <code>FilterExpression</code>. A <code>FilterExpression</code> determines which items within the results should be returned to you. All of the other results are discarded. </p> <p> A <code>Query</code> operation always returns a result set. If no matching items are found, the result set will be empty. Queries that do not return results consume the minimum number of read capacity units for that type of read operation. </p> <note> <p> DynamoDB calculates the number of read capacity units consumed based on item size, not on the amount of data that is returned to an application. The number of capacity units consumed will be the same whether you request all of the attributes (the default behavior) or just some of them (using a projection expression). The number will also be the same whether or not you use a <code>FilterExpression</code>. </p> </note> <p> <code>Query</code> results are always sorted by the sort key value. If the data type of the sort key is Number, the results are returned in numeric order; otherwise, the results are returned in order of UTF-8 bytes. By default, the sort order is ascending. To reverse the order, set the <code>ScanIndexForward</code> parameter to false. </p> <p> A single <code>Query</code> operation will read up to the maximum number of items set (if using the <code>Limit</code> parameter) or a maximum of 1 MB of data and then apply any filtering to the results using <code>FilterExpression</code>. If <code>LastEvaluatedKey</code> is present in the response, you will need to paginate the result set. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.html#Query.Pagination\">Paginating the Results</a> in the <i>Amazon DynamoDB Developer Guide</i>. </p> <p> <code>FilterExpression</code> is applied after a <code>Query</code> finishes, but before the results are returned. A <code>FilterExpression</code> cannot contain partition key or sort key attributes. You need to specify those attributes in the <code>KeyConditionExpression</code>. </p> <note> <p> A <code>Query</code> operation can return an empty result set and a <code>LastEvaluatedKey</code> if all the items read for the page of results are filtered out. </p> </note> <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 the <code>ConsistentRead</code> parameter to <code>true</code> and obtain a strongly consistent result. Global secondary indexes support eventually consistent reads only, so do not specify <code>ConsistentRead</code> when querying a global secondary index.</p>",
"RestoreTableFromBackup": "<p>Creates a new table from an existing backup. Any number of users can execute up to 10 concurrent restores in a given account. </p> <p>You can call <code>RestoreTableFromBackup</code> at a maximum rate of 10 times per second.</p> <p>You must manually set up the following on the restored table:</p> <ul> <li> <p>Auto scaling policies</p> </li> <li> <p>IAM policies</p> </li> <li> <p>Cloudwatch metrics and alarms</p> </li> <li> <p>Tags</p> </li> <li> <p>Stream settings</p> </li> <li> <p>Time to Live (TTL) settings</p> </li> </ul>",
"RestoreTableFromBackup": "<p>Creates a new table from an existing backup. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account. </p> <p>You can call <code>RestoreTableFromBackup</code> at a maximum rate of 10 times per second.</p> <p>You must manually set up the following on the restored table:</p> <ul> <li> <p>Auto scaling policies</p> </li> <li> <p>IAM policies</p> </li> <li> <p>Cloudwatch metrics and alarms</p> </li> <li> <p>Tags</p> </li> <li> <p>Stream settings</p> </li> <li> <p>Time to Live (TTL) settings</p> </li> </ul>",
"RestoreTableToPointInTime": "<p>Restores the specified table to the specified point in time within <code>EarliestRestorableDateTime</code> and <code>LatestRestorableDateTime</code>. You can restore your table to any point in time during the last 35 days. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account. </p> <p> When you restore using point in time recovery, DynamoDB restores your table data to the state based on the selected date and time (day:hour:minute:second) to a new table. </p> <p> Along with data, the following are also included on the new restored table using point in time recovery: </p> <ul> <li> <p>Global secondary indexes (GSIs)</p> </li> <li> <p>Local secondary indexes (LSIs)</p> </li> <li> <p>Provisioned read and write capacity</p> </li> <li> <p>Encryption settings</p> <important> <p> All these settings come from the current settings of the source table at the time of restore. </p> </important> </li> </ul> <p>You must manually set up the following on the restored table:</p> <ul> <li> <p>Auto scaling policies</p> </li> <li> <p>IAM policies</p> </li> <li> <p>Cloudwatch metrics and alarms</p> </li> <li> <p>Tags</p> </li> <li> <p>Stream settings</p> </li> <li> <p>Time to Live (TTL) settings</p> </li> <li> <p>Point in time recovery settings</p> </li> </ul>",
"Scan": "<p>The <code>Scan</code> operation returns one or more items and item attributes by accessing every item in a table or a secondary index. To have DynamoDB return fewer items, you can provide a <code>FilterExpression</code> operation.</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 as a <code>LastEvaluatedKey</code> value 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>A single <code>Scan</code> operation will read up to the maximum number of items set (if using the <code>Limit</code> parameter) or a maximum of 1 MB of data and then apply any filtering to the results using <code>FilterExpression</code>. If <code>LastEvaluatedKey</code> is present in the response, you will need to paginate the result set. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.Pagination\">Paginating the Results</a> in the <i>Amazon DynamoDB Developer Guide</i>. </p> <p> <code>Scan</code> operations proceed sequentially; however, for faster performance on a large table or secondary index, applications can request a parallel <code>Scan</code> operation by providing the <code>Segment</code> and <code>TotalSegments</code> parameters. For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.ParallelScan\">Parallel Scan</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p> <p> <code>Scan</code> uses eventually consistent reads when accessing the data in a table; therefore, the result set might not include the changes to data in the table immediately before the operation began. If you need a consistent copy of the data, as of the time that the <code>Scan</code> begins, you can set the <code>ConsistentRead</code> parameter to <code>true</code>.</p>",
"TagResource": "<p>Associate a set of tags with an Amazon DynamoDB resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking. You can call TagResource up to 5 times per second, per account. </p> <p>For an overview on tagging DynamoDB resources, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html\">Tagging for DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
"UntagResource": "<p>Removes the association of tags from an Amazon DynamoDB resource. You can call UntagResource up to 5 times per second, per account. </p> <p>For an overview on tagging DynamoDB resources, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html\">Tagging for DynamoDB</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>",
"UpdateGlobalTable": "<p>Adds or removes replicas in the specified global table. The global table must already exist to be able to use this operation. Any replica to be added must be empty, must have the same name as the global table, must have the same key schema, must have DynamoDB Streams enabled, and cannot have any local secondary indexes (LSIs).</p> <note> <p>Although you can use <code>UpdateGlobalTable</code> to add replicas and remove replicas in a single request, for simplicity we recommend that you issue separate requests for adding or removing replicas.</p> </note>",
"UpdateContinuousBackups": "<p> <code>UpdateContinuousBackups</code> enables or disables point in time recovery for the specified table. A successful <code>UpdateContinuousBackups</code> call returns the current <code>ContinuousBackupsDescription</code>. Continuous backups are <code>ENABLED</code> on all tables at table creation. If point in time recovery is enabled, <code>PointInTimeRecoveryStatus</code> will be set to ENABLED.</p> <p> Once continuous backups and point in time recovery are enabled, you can restore to any point in time within <code>EarliestRestorableDateTime</code> and <code>LatestRestorableDateTime</code>. </p> <p> <code>LatestRestorableDateTime</code> is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days.. </p>",
"UpdateGlobalTable": "<p>Adds or removes replicas in the specified global table. The global table must already exist to be able to use this operation. Any replica to be added must be empty, must have the same name as the global table, must have the same key schema, and must have DynamoDB Streams enabled and must have same provisioned and maximum write capacity units.</p> <note> <p>Although you can use <code>UpdateGlobalTable</code> to add replicas and remove replicas in a single request, for simplicity we recommend that you issue separate requests for adding or removing replicas.</p> </note> <p> If global secondary indexes are specified, then the following conditions must also be met: </p> <ul> <li> <p> The global secondary indexes must have the same name. </p> </li> <li> <p> The global secondary indexes must have the same hash key and sort key (if present). </p> </li> <li> <p> The global secondary indexes must have the same provisioned and maximum write capacity units. </p> </li> </ul>",
"UpdateGlobalTableSettings": "<p>Updates settings for a global table.</p>",
"UpdateItem": "<p>Edits an existing item's attributes, or adds a new item to the table if it does not already exist. You can put, delete, or add attribute values. You can also perform a conditional update on an existing item (insert a new attribute name-value pair if it doesn't exist, or replace an existing name-value pair if it has certain expected attribute values).</p> <p>You can also return the item's attribute values in the same <code>UpdateItem</code> operation using the <code>ReturnValues</code> parameter.</p>",
"UpdateTable": "<p>Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table.</p> <p>You can only perform one of the following operations at once:</p> <ul> <li> <p>Modify the provisioned throughput settings of the table.</p> </li> <li> <p>Enable or disable Streams on the table.</p> </li> <li> <p>Remove a global secondary index from the table.</p> </li> <li> <p>Create a new global secondary index on the table. Once the index begins backfilling, you can use <code>UpdateTable</code> to perform other operations.</p> </li> </ul> <p> <code>UpdateTable</code> is an asynchronous operation; while it is executing, the table status changes from <code>ACTIVE</code> to <code>UPDATING</code>. While it is <code>UPDATING</code>, you cannot issue another <code>UpdateTable</code> request. When the table returns to the <code>ACTIVE</code> state, the <code>UpdateTable</code> operation is complete.</p>",
"UpdateTimeToLive": "<p>The UpdateTimeToLive method will enable or disable TTL for the specified table. A successful <code>UpdateTimeToLive</code> call returns the current <code>TimeToLiveSpecification</code>; it may take up to one hour for the change to fully process. Any additional <code>UpdateTimeToLive</code> calls for the same table during this one hour duration result in a <code>ValidationException</code>. </p> <p>TTL compares the current time in epoch time format to the time stored in the TTL attribute of an item. If the epoch time value stored in the attribute is less than the current time, the item is marked as expired and subsequently deleted.</p> <note> <p> The epoch time format is the number of seconds elapsed since 12:00:00 AM January 1st, 1970 UTC. </p> </note> <p>DynamoDB deletes expired items on a best-effort basis to ensure availability of throughput for other data operations. </p> <important> <p>DynamoDB typically deletes expired items within two days of expiration. The exact duration within which an item gets deleted after expiration is specific to the nature of the workload. Items that have expired and not been deleted will still show up in reads, queries, and scans.</p> </important> <p>As items are deleted, they are removed from any Local Secondary Index and Global Secondary Index immediately in the same eventually consistent way as a standard delete operation.</p> <p>For more information, see <a href=\"http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html\">Time To Live</a> in the Amazon DynamoDB Developer Guide. </p>"
@ -275,7 +279,9 @@
"base": null,
"refs": {
"ExpectedAttributeValue$Exists": "<p>Causes DynamoDB to evaluate the value before attempting a conditional operation:</p> <ul> <li> <p>If <code>Exists</code> 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 <code>ConditionalCheckFailedException</code>.</p> </li> <li> <p>If <code>Exists</code> is <code>false</code>, DynamoDB assumes that the attribute value does not 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 <code>ConditionalCheckFailedException</code>.</p> </li> </ul> <p>The default setting for <code>Exists</code> is <code>true</code>. If you supply a <code>Value</code> all by itself, DynamoDB assumes the attribute exists: You don't have to set <code>Exists</code> to <code>true</code>, because it is implied.</p> <p>DynamoDB returns a <code>ValidationException</code> if:</p> <ul> <li> <p> <code>Exists</code> is <code>true</code> but there is no <code>Value</code> to check. (You expect a value to exist, but don't specify what that value is.)</p> </li> <li> <p> <code>Exists</code> is <code>false</code> but you also provide a <code>Value</code>. (You cannot expect an attribute to have a value, while also expecting it not to exist.)</p> </li> </ul>",
"QueryInput$ScanIndexForward": "<p>Specifies the order for index traversal: If <code>true</code> (default), the traversal is performed in ascending order; if <code>false</code>, the traversal is performed in descending order. </p> <p>Items with the same partition key value are stored in sorted order by sort key. If the sort key data type is Number, the results are stored in numeric order. For type String, the results are stored in order of ASCII character code values. For type Binary, DynamoDB treats each byte of the binary data as unsigned.</p> <p>If <code>ScanIndexForward</code> is <code>true</code>, DynamoDB returns the results in the order in which they are stored (by sort key value). This is the default behavior. If <code>ScanIndexForward</code> is <code>false</code>, DynamoDB reads the results in reverse order by sort key value, and then returns the results to the client.</p>"
"PointInTimeRecoverySpecification$PointInTimeRecoveryEnabled": "<p>Indicates whether point in time recovery is enabled (true) or disabled (false) on the table.</p>",
"QueryInput$ScanIndexForward": "<p>Specifies the order for index traversal: If <code>true</code> (default), the traversal is performed in ascending order; if <code>false</code>, the traversal is performed in descending order. </p> <p>Items with the same partition key value are stored in sorted order by sort key. If the sort key data type is Number, the results are stored in numeric order. For type String, the results are stored in order of UTF-8 bytes. For type Binary, DynamoDB treats each byte of the binary data as unsigned.</p> <p>If <code>ScanIndexForward</code> is <code>true</code>, DynamoDB returns the results in the order in which they are stored (by sort key value). This is the default behavior. If <code>ScanIndexForward</code> is <code>false</code>, DynamoDB reads the results in reverse order by sort key value, and then returns the results to the client.</p>",
"RestoreTableToPointInTimeInput$UseLatestRestorableTime": "<p>Restore the table to the latest possible time. <code>LatestRestorableDateTime</code> is typically 5 minutes before the current time. </p>"
}
},
"Capacity": {
@ -360,15 +366,16 @@
}
},
"ContinuousBackupsDescription": {
"base": "<p>Represents the backup and restore settings on the table when the backup was created.</p>",
"base": "<p>Represents the continuous backups and point in time recovery settings on the table.</p>",
"refs": {
"DescribeContinuousBackupsOutput$ContinuousBackupsDescription": "<p> <code>ContinuousBackupsDescription</code> can be one of the following : ENABLED, DISABLED. </p>"
"DescribeContinuousBackupsOutput$ContinuousBackupsDescription": "<p> <code>ContinuousBackupsDescription</code> can be one of the following : ENABLED, DISABLED. </p>",
"UpdateContinuousBackupsOutput$ContinuousBackupsDescription": "<p>Represents the continuous backups and point in time recovery settings on the table.</p>"
}
},
"ContinuousBackupsStatus": {
"base": null,
"refs": {
"ContinuousBackupsDescription$ContinuousBackupsStatus": "<p>ContinuousBackupsStatus can be one of the following states : ENABLED, DISABLED</p>"
"ContinuousBackupsDescription$ContinuousBackupsStatus": "<p> <code>ContinuousBackupsStatus</code> can be one of the following states : ENABLED, DISABLED</p>"
}
},
"ContinuousBackupsUnavailableException": {
@ -422,8 +429,12 @@
"base": null,
"refs": {
"GlobalTableDescription$CreationDateTime": "<p>The creation time of the global table.</p>",
"PointInTimeRecoveryDescription$EarliestRestorableDateTime": "<p>Specifies the earliest point in time you can restore your table to. It You can restore your table to any point in time during the last 35 days. </p>",
"PointInTimeRecoveryDescription$LatestRestorableDateTime": "<p> <code>LatestRestorableDateTime</code> is typically 5 minutes before the current time. </p>",
"ProvisionedThroughputDescription$LastIncreaseDateTime": "<p>The date and time of the last provisioned throughput increase for this table.</p>",
"ProvisionedThroughputDescription$LastDecreaseDateTime": "<p>The date and time of the last provisioned throughput decrease for this table.</p>",
"RestoreSummary$RestoreDateTime": "<p>Point in time or source backup time.</p>",
"RestoreTableToPointInTimeInput$RestoreDateTime": "<p>Time in the past to restore the table to.</p>",
"TableDescription$CreationDateTime": "<p>The date and time when the table was created, in <a href=\"http://www.epochconverter.com/\">UNIX epoch time</a> format.</p>"
}
},
@ -505,6 +516,16 @@
"refs": {
}
},
"DescribeGlobalTableSettingsInput": {
"base": null,
"refs": {
}
},
"DescribeGlobalTableSettingsOutput": {
"base": null,
"refs": {
}
},
"DescribeLimitsInput": {
"base": "<p>Represents the input of a <code>DescribeLimits</code> operation. Has no content.</p>",
"refs": {
@ -544,9 +565,12 @@
"ContinuousBackupsUnavailableException$message": null,
"GlobalTableAlreadyExistsException$message": null,
"GlobalTableNotFoundException$message": null,
"IndexNotFoundException$message": null,
"InternalServerError$message": "<p>The server encountered an internal error trying to fulfill the request.</p>",
"InvalidRestoreTimeException$message": null,
"ItemCollectionSizeLimitExceededException$message": "<p>The total size of an item collection has exceeded the maximum limit of 10 gigabytes.</p>",
"LimitExceededException$message": "<p>Too many operations for a given subscriber.</p>",
"PointInTimeRecoveryUnavailableException$message": null,
"ProvisionedThroughputExceededException$message": "<p>You exceeded your maximum allowed provisioned throughput.</p>",
"ReplicaAlreadyExistsException$message": null,
"ReplicaNotFoundException$message": null,
@ -695,6 +719,18 @@
"UpdateGlobalTableOutput$GlobalTableDescription": "<p>Contains the details of the global table.</p>"
}
},
"GlobalTableGlobalSecondaryIndexSettingsUpdate": {
"base": "<p>Represents the settings of a global secondary index for a global table that will be modified.</p>",
"refs": {
"GlobalTableGlobalSecondaryIndexSettingsUpdateList$member": null
}
},
"GlobalTableGlobalSecondaryIndexSettingsUpdateList": {
"base": null,
"refs": {
"UpdateGlobalTableSettingsInput$GlobalTableGlobalSecondaryIndexSettingsUpdate": "<p>Represents the settings of a global secondary index for a global table that will be modified.</p>"
}
},
"GlobalTableList": {
"base": null,
"refs": {
@ -720,19 +756,28 @@
"GlobalSecondaryIndex$IndexName": "<p>The name of the global secondary index. The name must be unique among all other indexes on this table.</p>",
"GlobalSecondaryIndexDescription$IndexName": "<p>The name of the global secondary index.</p>",
"GlobalSecondaryIndexInfo$IndexName": "<p>The name of the global secondary index.</p>",
"GlobalTableGlobalSecondaryIndexSettingsUpdate$IndexName": "<p>The name of the global secondary index. The name must be unique among all other indexes on this table.</p>",
"LocalSecondaryIndex$IndexName": "<p>The name of the local secondary index. The name must be unique among all other indexes on this table.</p>",
"LocalSecondaryIndexDescription$IndexName": "<p>Represents the name of the local secondary index.</p>",
"LocalSecondaryIndexInfo$IndexName": "<p>Represents the name of the local secondary index.</p>",
"QueryInput$IndexName": "<p>The name of an index to query. This index can be any local secondary index or global secondary index on the table. Note that if you use the <code>IndexName</code> parameter, you must also provide <code>TableName.</code> </p>",
"ReplicaGlobalSecondaryIndexSettingsDescription$IndexName": "<p>The name of the global secondary index. The name must be unique among all other indexes on this table.</p>",
"ReplicaGlobalSecondaryIndexSettingsUpdate$IndexName": "<p>The name of the global secondary index. The name must be unique among all other indexes on this table.</p>",
"ScanInput$IndexName": "<p>The name of a secondary index to scan. This index can be any local secondary index or global secondary index. Note that if you use the <code>IndexName</code> parameter, you must also provide <code>TableName</code>.</p>",
"SecondaryIndexesCapacityMap$key": null,
"UpdateGlobalSecondaryIndexAction$IndexName": "<p>The name of the global secondary index to be updated.</p>"
}
},
"IndexNotFoundException": {
"base": "<p>The operation tried to access a nonexistent index.</p>",
"refs": {
}
},
"IndexStatus": {
"base": null,
"refs": {
"GlobalSecondaryIndexDescription$IndexStatus": "<p>The current state of the global secondary index:</p> <ul> <li> <p> <code>CREATING</code> - The index is being created.</p> </li> <li> <p> <code>UPDATING</code> - The index is being updated.</p> </li> <li> <p> <code>DELETING</code> - The index is being deleted.</p> </li> <li> <p> <code>ACTIVE</code> - The index is ready for use.</p> </li> </ul>"
"GlobalSecondaryIndexDescription$IndexStatus": "<p>The current state of the global secondary index:</p> <ul> <li> <p> <code>CREATING</code> - The index is being created.</p> </li> <li> <p> <code>UPDATING</code> - The index is being updated.</p> </li> <li> <p> <code>DELETING</code> - The index is being deleted.</p> </li> <li> <p> <code>ACTIVE</code> - The index is ready for use.</p> </li> </ul>",
"ReplicaGlobalSecondaryIndexSettingsDescription$IndexStatus": "<p> The current status of the global secondary index:</p> <ul> <li> <p> <code>CREATING</code> - The global secondary index is being created.</p> </li> <li> <p> <code>UPDATING</code> - The global secondary index is being updated.</p> </li> <li> <p> <code>DELETING</code> - The global secondary index is being deleted.</p> </li> <li> <p> <code>ACTIVE</code> - The global secondary index is ready for use.</p> </li> </ul>"
}
},
"Integer": {
@ -749,6 +794,11 @@
"refs": {
}
},
"InvalidRestoreTimeException": {
"base": "<p>An invalid restore time was specified. RestoreDateTime must be between EarliestRestorableDateTime and LatestRestorableDateTime.</p>",
"refs": {
}
},
"ItemCollectionKeyAttributeMap": {
"base": null,
"refs": {
@ -880,7 +930,7 @@
}
},
"LimitExceededException": {
"base": "<p>Up to 50 <code>CreateBackup</code> operations are allowed per second, per account. There is no limit to the number of daily on-demand backups that can be taken. </p> <p>Up to 10 simultaneous table operations are allowed per account. These operations include <code>CreateTable</code>, <code>UpdateTable</code>, <code>DeleteTable</code>,<code>UpdateTimeToLive</code>, and <code>RestoreTableFromBackup</code>. </p> <p>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> <p>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>",
"base": "<p>Up to 50 <code>CreateBackup</code> operations are allowed per second, per account. There is no limit to the number of daily on-demand backups that can be taken. </p> <p>Up to 10 simultaneous table operations are allowed per account. These operations include <code>CreateTable</code>, <code>UpdateTable</code>, <code>DeleteTable</code>,<code>UpdateTimeToLive</code>, <code>RestoreTableFromBackup</code>, and <code>RestoreTableToPointInTime</code>. </p> <p>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>",
"refs": {
}
},
@ -1028,6 +1078,29 @@
"AttributeValue$NS": "<p>An attribute of type Number Set. For example:</p> <p> <code>\"NS\": [\"42.2\", \"-19\", \"7.5\", \"3.14\"]</code> </p> <p>Numbers are sent across the network to DynamoDB as strings, to maximize compatibility across languages and libraries. However, DynamoDB treats them as number type attributes for mathematical operations.</p>"
}
},
"PointInTimeRecoveryDescription": {
"base": "<p>The description of the point in time settings applied to the table.</p>",
"refs": {
"ContinuousBackupsDescription$PointInTimeRecoveryDescription": "<p>The description of the point in time recovery settings applied to the table.</p>"
}
},
"PointInTimeRecoverySpecification": {
"base": "<p>Represents the settings used to enable point in time recovery.</p>",
"refs": {
"UpdateContinuousBackupsInput$PointInTimeRecoverySpecification": "<p>Represents the settings used to enable point in time recovery.</p>"
}
},
"PointInTimeRecoveryStatus": {
"base": null,
"refs": {
"PointInTimeRecoveryDescription$PointInTimeRecoveryStatus": "<p>The current state of point in time recovery:</p> <ul> <li> <p> <code>ENABLING</code> - Point in time recovery is being enabled.</p> </li> <li> <p> <code>ENABLED</code> - Point in time recovery is enabled.</p> </li> <li> <p> <code>DISABLED</code> - Point in time recovery is disabled.</p> </li> </ul>"
}
},
"PointInTimeRecoveryUnavailableException": {
"base": "<p>Point in time recovery has not yet been enabled for this source table.</p>",
"refs": {
}
},
"PositiveIntegerObject": {
"base": null,
"refs": {
@ -1043,11 +1116,19 @@
"DescribeLimitsOutput$AccountMaxWriteCapacityUnits": "<p>The maximum total write capacity units that your account allows you to provision across all of your tables in this region.</p>",
"DescribeLimitsOutput$TableMaxReadCapacityUnits": "<p>The maximum read capacity units that your account allows you to provision for a new table that you are creating in this region, including the read capacity units provisioned for its global secondary indexes (GSIs).</p>",
"DescribeLimitsOutput$TableMaxWriteCapacityUnits": "<p>The maximum write capacity units that your account allows you to provision for a new table that you are creating in this region, including the write capacity units provisioned for its global secondary indexes (GSIs).</p>",
"GlobalTableGlobalSecondaryIndexSettingsUpdate$ProvisionedWriteCapacityUnits": "<p>The maximum number of writes consumed per second before DynamoDB returns a <code>ThrottlingException.</code> </p>",
"ProvisionedThroughput$ReadCapacityUnits": "<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <code>ThrottlingException</code>. 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 <i>Amazon DynamoDB Developer Guide</i>.</p>",
"ProvisionedThroughput$WriteCapacityUnits": "<p>The maximum number of writes consumed per second before DynamoDB returns a <code>ThrottlingException</code>. 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 <i>Amazon DynamoDB Developer Guide</i>.</p>",
"ProvisionedThroughputDescription$NumberOfDecreasesToday": "<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 <i>Amazon DynamoDB Developer Guide</i>.</p>",
"ProvisionedThroughputDescription$ReadCapacityUnits": "<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <code>ThrottlingException</code>. Eventually consistent reads require less effort than strongly consistent reads, so a setting of 50 <code>ReadCapacityUnits</code> per second provides 100 eventually consistent <code>ReadCapacityUnits</code> per second.</p>",
"ProvisionedThroughputDescription$WriteCapacityUnits": "<p>The maximum number of writes consumed per second before DynamoDB returns a <code>ThrottlingException</code>.</p>"
"ProvisionedThroughputDescription$WriteCapacityUnits": "<p>The maximum number of writes consumed per second before DynamoDB returns a <code>ThrottlingException</code>.</p>",
"ReplicaGlobalSecondaryIndexSettingsDescription$ProvisionedReadCapacityUnits": "<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <code>ThrottlingException</code>.</p>",
"ReplicaGlobalSecondaryIndexSettingsDescription$ProvisionedWriteCapacityUnits": "<p>The maximum number of writes consumed per second before DynamoDB returns a <code>ThrottlingException</code>.</p>",
"ReplicaGlobalSecondaryIndexSettingsUpdate$ProvisionedReadCapacityUnits": "<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <code>ThrottlingException</code>.</p>",
"ReplicaSettingsDescription$ReplicaProvisionedReadCapacityUnits": "<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <code>ThrottlingException</code>. 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 <i>Amazon DynamoDB Developer Guide</i>. </p>",
"ReplicaSettingsDescription$ReplicaProvisionedWriteCapacityUnits": "<p>The maximum number of writes consumed per second before DynamoDB returns a <code>ThrottlingException</code>. 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 <i>Amazon DynamoDB Developer Guide</i>.</p>",
"ReplicaSettingsUpdate$ReplicaProvisionedReadCapacityUnits": "<p>The maximum number of strongly consistent reads consumed per second before DynamoDB returns a <code>ThrottlingException</code>. 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 <i>Amazon DynamoDB Developer Guide</i>. </p>",
"UpdateGlobalTableSettingsInput$GlobalTableProvisionedWriteCapacityUnits": "<p>The maximum number of writes consumed per second before DynamoDB returns a <code>ThrottlingException.</code> </p>"
}
},
"Projection": {
@ -1141,7 +1222,9 @@
"DeleteReplicaAction$RegionName": "<p>The region of the replica to be removed.</p>",
"ListGlobalTablesInput$RegionName": "<p>Lists the global tables in a specific region.</p>",
"Replica$RegionName": "<p>The region where the replica needs to be created.</p>",
"ReplicaDescription$RegionName": "<p>The name of the region.</p>"
"ReplicaDescription$RegionName": "<p>The name of the region.</p>",
"ReplicaSettingsDescription$RegionName": "<p>The region name of the replica.</p>",
"ReplicaSettingsUpdate$RegionName": "<p>The region of the replica to be added.</p>"
}
},
"Replica": {
@ -1167,6 +1250,30 @@
"GlobalTableDescription$ReplicationGroup": "<p>The regions where the global table has replicas.</p>"
}
},
"ReplicaGlobalSecondaryIndexSettingsDescription": {
"base": "<p>Represents the properties of a global secondary index.</p>",
"refs": {
"ReplicaGlobalSecondaryIndexSettingsDescriptionList$member": null
}
},
"ReplicaGlobalSecondaryIndexSettingsDescriptionList": {
"base": null,
"refs": {
"ReplicaSettingsDescription$ReplicaGlobalSecondaryIndexSettings": "<p>Replica global secondary index settings for the global table.</p>"
}
},
"ReplicaGlobalSecondaryIndexSettingsUpdate": {
"base": "<p>Represents the settings of a global secondary index for a global table that will be modified.</p>",
"refs": {
"ReplicaGlobalSecondaryIndexSettingsUpdateList$member": null
}
},
"ReplicaGlobalSecondaryIndexSettingsUpdateList": {
"base": null,
"refs": {
"ReplicaSettingsUpdate$ReplicaGlobalSecondaryIndexSettingsUpdate": "<p>Represents the settings of a global secondary index for a global table that will be modified.</p>"
}
},
"ReplicaList": {
"base": null,
"refs": {
@ -1179,6 +1286,37 @@
"refs": {
}
},
"ReplicaSettingsDescription": {
"base": "<p>Represents the properties of a replica.</p>",
"refs": {
"ReplicaSettingsDescriptionList$member": null
}
},
"ReplicaSettingsDescriptionList": {
"base": null,
"refs": {
"DescribeGlobalTableSettingsOutput$ReplicaSettings": "<p>The region specific settings for the global table.</p>",
"UpdateGlobalTableSettingsOutput$ReplicaSettings": "<p>The region specific settings for the global table.</p>"
}
},
"ReplicaSettingsUpdate": {
"base": "<p>Represents the settings for a global table in a region that will be modified.</p>",
"refs": {
"ReplicaSettingsUpdateList$member": null
}
},
"ReplicaSettingsUpdateList": {
"base": null,
"refs": {
"UpdateGlobalTableSettingsInput$ReplicaSettingsUpdate": "<p>Represents the settings for a global table in a region that will be modified.</p>"
}
},
"ReplicaStatus": {
"base": null,
"refs": {
"ReplicaSettingsDescription$ReplicaStatus": "<p>The current state of the region:</p> <ul> <li> <p> <code>CREATING</code> - The region is being created.</p> </li> <li> <p> <code>UPDATING</code> - The region is being updated.</p> </li> <li> <p> <code>DELETING</code> - The region is being deleted.</p> </li> <li> <p> <code>ACTIVE</code> - The region is ready for use.</p> </li> </ul>"
}
},
"ReplicaUpdate": {
"base": "<p>Represents one of the following:</p> <ul> <li> <p>A new replica to be added to an existing global table.</p> </li> <li> <p>New parameters for an existing replica.</p> </li> <li> <p>An existing replica to be removed from an existing global table.</p> </li> </ul>",
"refs": {
@ -1209,12 +1347,6 @@
"refs": {
}
},
"RestoreDateTime": {
"base": null,
"refs": {
"RestoreSummary$RestoreDateTime": "<p>Point in time or source backup time.</p>"
}
},
"RestoreInProgress": {
"base": null,
"refs": {
@ -1237,6 +1369,16 @@
"refs": {
}
},
"RestoreTableToPointInTimeInput": {
"base": null,
"refs": {
}
},
"RestoreTableToPointInTimeOutput": {
"base": null,
"refs": {
}
},
"ReturnConsumedCapacity": {
"base": "<p>Determines the level of detail about provisioned throughput consumption that is returned in the response:</p> <ul> <li> <p> <code>INDEXES</code> - The response includes the aggregate <code>ConsumedCapacity</code> for the operation, together with <code>ConsumedCapacity</code> for each table and secondary index that was accessed.</p> <p>Note that some operations, such as <code>GetItem</code> and <code>BatchGetItem</code>, do not access any indexes at all. In these cases, specifying <code>INDEXES</code> will only return <code>ConsumedCapacity</code> information for table(s).</p> </li> <li> <p> <code>TOTAL</code> - The response includes only the aggregate <code>ConsumedCapacity</code> for the operation.</p> </li> <li> <p> <code>NONE</code> - No <code>ConsumedCapacity</code> details are included in the response.</p> </li> </ul>",
"refs": {
@ -1396,7 +1538,7 @@
}
},
"TableAlreadyExistsException": {
"base": "<p>A table with the name already exists. </p>",
"base": "<p>A target table with the specified name already exists. </p>",
"refs": {
}
},
@ -1421,6 +1563,7 @@
"DeleteTableOutput$TableDescription": "<p>Represents the properties of a table.</p>",
"DescribeTableOutput$Table": "<p>The properties of the table.</p>",
"RestoreTableFromBackupOutput$TableDescription": "<p>The description of the table created from an existing backup.</p>",
"RestoreTableToPointInTimeOutput$TableDescription": "<p>Represents the properties of a table.</p>",
"UpdateTableOutput$TableDescription": "<p>Represents the properties of the table.</p>"
}
},
@ -1433,7 +1576,7 @@
}
},
"TableInUseException": {
"base": "<p>A table by that name is either being created or deleted. </p>",
"base": "<p>A target table with the specified name is either being created or deleted. </p>",
"refs": {
}
},
@ -1450,8 +1593,10 @@
"CreateTableInput$TableName": "<p>The name of the table to create.</p>",
"DeleteItemInput$TableName": "<p>The name of the table from which to delete the item.</p>",
"DeleteTableInput$TableName": "<p>The name of the table to delete.</p>",
"DescribeContinuousBackupsInput$TableName": "<p>Name of the table for which the customer wants to check the backup and restore settings.</p>",
"DescribeContinuousBackupsInput$TableName": "<p>Name of the table for which the customer wants to check the continuous backups and point in time recovery settings.</p>",
"DescribeGlobalTableInput$GlobalTableName": "<p>The name of the global table.</p>",
"DescribeGlobalTableSettingsInput$GlobalTableName": "<p>The name of the global table to describe.</p>",
"DescribeGlobalTableSettingsOutput$GlobalTableName": "<p>The name of the global table.</p>",
"DescribeTableInput$TableName": "<p>The name of the table to describe.</p>",
"DescribeTimeToLiveInput$TableName": "<p>The name of the table to be described.</p>",
"GetItemInput$TableName": "<p>The name of the table containing the requested item.</p>",
@ -1466,11 +1611,16 @@
"PutItemInput$TableName": "<p>The name of the table to contain the item.</p>",
"QueryInput$TableName": "<p>The name of the table containing the requested items.</p>",
"RestoreTableFromBackupInput$TargetTableName": "<p>The name of the new table to which the backup must be restored.</p>",
"RestoreTableToPointInTimeInput$SourceTableName": "<p>Name of the source table that is being restored.</p>",
"RestoreTableToPointInTimeInput$TargetTableName": "<p>The name of the new table to which it must be restored to.</p>",
"ScanInput$TableName": "<p>The name of the table containing the requested items; or, if you provide <code>IndexName</code>, the name of the table to which that index belongs.</p>",
"SourceTableDetails$TableName": "<p>The name of the table for which the backup was created. </p>",
"TableDescription$TableName": "<p>The name of the table.</p>",
"TableNameList$member": null,
"UpdateContinuousBackupsInput$TableName": "<p>The name of the table.</p>",
"UpdateGlobalTableInput$GlobalTableName": "<p>The global table name.</p>",
"UpdateGlobalTableSettingsInput$GlobalTableName": "<p>The name of the global table</p>",
"UpdateGlobalTableSettingsOutput$GlobalTableName": "<p>The name of the global table.</p>",
"UpdateItemInput$TableName": "<p>The name of the table containing the item to update.</p>",
"UpdateTableInput$TableName": "<p>The name of the table to be updated.</p>",
"UpdateTimeToLiveInput$TableName": "<p>The name of the table to be configured.</p>"
@ -1483,7 +1633,7 @@
}
},
"TableNotFoundException": {
"base": "<p>A table with the name <code>TableName</code> does not currently exist within the subscriber's account.</p>",
"base": "<p>A source table with the name <code>TableName</code> does not currently exist within the subscriber's account.</p>",
"refs": {
}
},
@ -1580,6 +1730,16 @@
"refs": {
}
},
"UpdateContinuousBackupsInput": {
"base": null,
"refs": {
}
},
"UpdateContinuousBackupsOutput": {
"base": null,
"refs": {
}
},
"UpdateExpression": {
"base": null,
"refs": {
@ -1602,6 +1762,16 @@
"refs": {
}
},
"UpdateGlobalTableSettingsInput": {
"base": null,
"refs": {
}
},
"UpdateGlobalTableSettingsOutput": {
"base": null,
"refs": {
}
},
"UpdateItemInput": {
"base": "<p>Represents the input of an <code>UpdateItem</code> operation.</p>",
"refs": {