@aws-sdk/client-dynamodb 3.288.0 → 3.290.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist-types/commands/BatchExecuteStatementCommand.d.ts +9 -0
- package/dist-types/commands/BatchGetItemCommand.d.ts +85 -0
- package/dist-types/commands/BatchWriteItemCommand.d.ts +84 -0
- package/dist-types/commands/CreateBackupCommand.d.ts +34 -0
- package/dist-types/commands/CreateGlobalTableCommand.d.ts +26 -0
- package/dist-types/commands/CreateTableCommand.d.ts +94 -0
- package/dist-types/commands/DeleteBackupCommand.d.ts +26 -0
- package/dist-types/commands/DeleteItemCommand.d.ts +59 -0
- package/dist-types/commands/DeleteTableCommand.d.ts +54 -0
- package/dist-types/commands/DescribeBackupCommand.d.ts +9 -0
- package/dist-types/commands/DescribeContinuousBackupsCommand.d.ts +10 -0
- package/dist-types/commands/DescribeContributorInsightsCommand.d.ts +8 -0
- package/dist-types/commands/DescribeEndpointsCommand.d.ts +1 -0
- package/dist-types/commands/DescribeExportCommand.d.ts +20 -0
- package/dist-types/commands/DescribeGlobalTableCommand.d.ts +9 -0
- package/dist-types/commands/DescribeGlobalTableSettingsCommand.d.ts +9 -0
- package/dist-types/commands/DescribeImportCommand.d.ts +6 -0
- package/dist-types/commands/DescribeKinesisStreamingDestinationCommand.d.ts +10 -0
- package/dist-types/commands/DescribeLimitsCommand.d.ts +23 -0
- package/dist-types/commands/DescribeTableCommand.d.ts +57 -0
- package/dist-types/commands/DescribeTableReplicaAutoScalingCommand.d.ts +8 -0
- package/dist-types/commands/DescribeTimeToLiveCommand.d.ts +10 -0
- package/dist-types/commands/DisableKinesisStreamingDestinationCommand.d.ts +28 -0
- package/dist-types/commands/EnableKinesisStreamingDestinationCommand.d.ts +28 -0
- package/dist-types/commands/ExecuteStatementCommand.d.ts +34 -0
- package/dist-types/commands/ExecuteTransactionCommand.d.ts +321 -0
- package/dist-types/commands/ExportTableToPointInTimeCommand.d.ts +31 -0
- package/dist-types/commands/GetItemCommand.d.ts +55 -0
- package/dist-types/commands/ImportTableCommand.d.ts +26 -0
- package/dist-types/commands/ListBackupsCommand.d.ts +6 -0
- package/dist-types/commands/ListContributorInsightsCommand.d.ts +8 -0
- package/dist-types/commands/ListExportsCommand.d.ts +17 -0
- package/dist-types/commands/ListGlobalTablesCommand.d.ts +6 -0
- package/dist-types/commands/ListImportsCommand.d.ts +14 -0
- package/dist-types/commands/ListTablesCommand.d.ts +25 -0
- package/dist-types/commands/ListTagsOfResourceCommand.d.ts +10 -0
- package/dist-types/commands/PutItemCommand.d.ts +63 -0
- package/dist-types/commands/QueryCommand.d.ts +53 -0
- package/dist-types/commands/RestoreTableFromBackupCommand.d.ts +33 -0
- package/dist-types/commands/RestoreTableToPointInTimeCommand.d.ts +37 -0
- package/dist-types/commands/ScanCommand.d.ts +68 -0
- package/dist-types/commands/TagResourceCommand.d.ts +28 -0
- package/dist-types/commands/TransactGetItemsCommand.d.ts +254 -0
- package/dist-types/commands/TransactWriteItemsCommand.d.ts +323 -0
- package/dist-types/commands/UntagResourceCommand.d.ts +28 -0
- package/dist-types/commands/UpdateContinuousBackupsCommand.d.ts +13 -0
- package/dist-types/commands/UpdateContributorInsightsCommand.d.ts +8 -0
- package/dist-types/commands/UpdateGlobalTableCommand.d.ts +19 -0
- package/dist-types/commands/UpdateGlobalTableSettingsCommand.d.ts +33 -0
- package/dist-types/commands/UpdateItemCommand.d.ts +83 -0
- package/dist-types/commands/UpdateTableCommand.d.ts +80 -0
- package/dist-types/commands/UpdateTableReplicaAutoScalingCommand.d.ts +26 -0
- package/dist-types/commands/UpdateTimeToLiveCommand.d.ts +28 -0
- package/package.json +31 -31
|
@@ -55,6 +55,260 @@ export interface TransactGetItemsCommandOutput extends TransactGetItemsOutput, _
|
|
|
55
55
|
* @see {@link TransactGetItemsCommandOutput} for command's `response` shape.
|
|
56
56
|
* @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
|
|
57
57
|
*
|
|
58
|
+
* @throws {@link InternalServerError} (server fault)
|
|
59
|
+
* <p>An error occurred on the server side.</p>
|
|
60
|
+
*
|
|
61
|
+
* @throws {@link InvalidEndpointException} (client fault)
|
|
62
|
+
*
|
|
63
|
+
* @throws {@link ProvisionedThroughputExceededException} (client fault)
|
|
64
|
+
* <p>Your request rate is too high. The Amazon Web Services SDKs for DynamoDB
|
|
65
|
+
* automatically retry requests that receive this exception. Your request is eventually
|
|
66
|
+
* successful, unless your retry queue is too large to finish. Reduce the frequency of
|
|
67
|
+
* requests and use exponential backoff. For more information, go to <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html#Programming.Errors.RetryAndBackoff">Error Retries and Exponential Backoff</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
|
|
68
|
+
*
|
|
69
|
+
* @throws {@link RequestLimitExceeded} (client fault)
|
|
70
|
+
* <p>Throughput exceeds the current throughput quota for your account. Please contact
|
|
71
|
+
* <a href="https://aws.amazon.com/support">Amazon Web Services Support</a> to request a
|
|
72
|
+
* quota increase.</p>
|
|
73
|
+
*
|
|
74
|
+
* @throws {@link ResourceNotFoundException} (client fault)
|
|
75
|
+
* <p>The operation tried to access a nonexistent table or index. The resource might not
|
|
76
|
+
* be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
|
|
77
|
+
*
|
|
78
|
+
* @throws {@link TransactionCanceledException} (client fault)
|
|
79
|
+
* <p>The entire transaction request was canceled.</p>
|
|
80
|
+
* <p>DynamoDB cancels a <code>TransactWriteItems</code> request under the following
|
|
81
|
+
* circumstances:</p>
|
|
82
|
+
* <ul>
|
|
83
|
+
* <li>
|
|
84
|
+
* <p>A condition in one of the condition expressions is not met.</p>
|
|
85
|
+
* </li>
|
|
86
|
+
* <li>
|
|
87
|
+
* <p>A table in the <code>TransactWriteItems</code> request is in a different
|
|
88
|
+
* account or region.</p>
|
|
89
|
+
* </li>
|
|
90
|
+
* <li>
|
|
91
|
+
* <p>More than one action in the <code>TransactWriteItems</code> operation
|
|
92
|
+
* targets the same item.</p>
|
|
93
|
+
* </li>
|
|
94
|
+
* <li>
|
|
95
|
+
* <p>There is insufficient provisioned capacity for the transaction to be
|
|
96
|
+
* completed.</p>
|
|
97
|
+
* </li>
|
|
98
|
+
* <li>
|
|
99
|
+
* <p>An item size becomes too large (larger than 400 KB), or a local secondary
|
|
100
|
+
* index (LSI) becomes too large, or a similar validation error occurs because of
|
|
101
|
+
* changes made by the transaction.</p>
|
|
102
|
+
* </li>
|
|
103
|
+
* <li>
|
|
104
|
+
* <p>There is a user error, such as an invalid data format.</p>
|
|
105
|
+
* </li>
|
|
106
|
+
* </ul>
|
|
107
|
+
* <p>DynamoDB cancels a <code>TransactGetItems</code> request under the
|
|
108
|
+
* following circumstances:</p>
|
|
109
|
+
* <ul>
|
|
110
|
+
* <li>
|
|
111
|
+
* <p>There is an ongoing <code>TransactGetItems</code> operation that conflicts
|
|
112
|
+
* with a concurrent <code>PutItem</code>, <code>UpdateItem</code>,
|
|
113
|
+
* <code>DeleteItem</code> or <code>TransactWriteItems</code> request. In this
|
|
114
|
+
* case the <code>TransactGetItems</code> operation fails with a
|
|
115
|
+
* <code>TransactionCanceledException</code>.</p>
|
|
116
|
+
* </li>
|
|
117
|
+
* <li>
|
|
118
|
+
* <p>A table in the <code>TransactGetItems</code> request is in a different
|
|
119
|
+
* account or region.</p>
|
|
120
|
+
* </li>
|
|
121
|
+
* <li>
|
|
122
|
+
* <p>There is insufficient provisioned capacity for the transaction to be
|
|
123
|
+
* completed.</p>
|
|
124
|
+
* </li>
|
|
125
|
+
* <li>
|
|
126
|
+
* <p>There is a user error, such as an invalid data format.</p>
|
|
127
|
+
* </li>
|
|
128
|
+
* </ul>
|
|
129
|
+
* <note>
|
|
130
|
+
* <p>If using Java, DynamoDB lists the cancellation reasons on the
|
|
131
|
+
* <code>CancellationReasons</code> property. This property is not set for other
|
|
132
|
+
* languages. Transaction cancellation reasons are ordered in the order of requested
|
|
133
|
+
* items, if an item has no error it will have <code>None</code> code and
|
|
134
|
+
* <code>Null</code> message.</p>
|
|
135
|
+
* </note>
|
|
136
|
+
* <p>Cancellation reason codes and possible error messages:</p>
|
|
137
|
+
* <ul>
|
|
138
|
+
* <li>
|
|
139
|
+
* <p>No Errors:</p>
|
|
140
|
+
* <ul>
|
|
141
|
+
* <li>
|
|
142
|
+
* <p>Code: <code>None</code>
|
|
143
|
+
* </p>
|
|
144
|
+
* </li>
|
|
145
|
+
* <li>
|
|
146
|
+
* <p>Message: <code>null</code>
|
|
147
|
+
* </p>
|
|
148
|
+
* </li>
|
|
149
|
+
* </ul>
|
|
150
|
+
* </li>
|
|
151
|
+
* <li>
|
|
152
|
+
* <p>Conditional Check Failed:</p>
|
|
153
|
+
* <ul>
|
|
154
|
+
* <li>
|
|
155
|
+
* <p>Code: <code>ConditionalCheckFailed</code>
|
|
156
|
+
* </p>
|
|
157
|
+
* </li>
|
|
158
|
+
* <li>
|
|
159
|
+
* <p>Message: The conditional request failed. </p>
|
|
160
|
+
* </li>
|
|
161
|
+
* </ul>
|
|
162
|
+
* </li>
|
|
163
|
+
* <li>
|
|
164
|
+
* <p>Item Collection Size Limit Exceeded:</p>
|
|
165
|
+
* <ul>
|
|
166
|
+
* <li>
|
|
167
|
+
* <p>Code: <code>ItemCollectionSizeLimitExceeded</code>
|
|
168
|
+
* </p>
|
|
169
|
+
* </li>
|
|
170
|
+
* <li>
|
|
171
|
+
* <p>Message: Collection size exceeded.</p>
|
|
172
|
+
* </li>
|
|
173
|
+
* </ul>
|
|
174
|
+
* </li>
|
|
175
|
+
* <li>
|
|
176
|
+
* <p>Transaction Conflict:</p>
|
|
177
|
+
* <ul>
|
|
178
|
+
* <li>
|
|
179
|
+
* <p>Code: <code>TransactionConflict</code>
|
|
180
|
+
* </p>
|
|
181
|
+
* </li>
|
|
182
|
+
* <li>
|
|
183
|
+
* <p>Message: Transaction is ongoing for the item.</p>
|
|
184
|
+
* </li>
|
|
185
|
+
* </ul>
|
|
186
|
+
* </li>
|
|
187
|
+
* <li>
|
|
188
|
+
* <p>Provisioned Throughput Exceeded:</p>
|
|
189
|
+
* <ul>
|
|
190
|
+
* <li>
|
|
191
|
+
* <p>Code: <code>ProvisionedThroughputExceeded</code>
|
|
192
|
+
* </p>
|
|
193
|
+
* </li>
|
|
194
|
+
* <li>
|
|
195
|
+
* <p>Messages:</p>
|
|
196
|
+
* <ul>
|
|
197
|
+
* <li>
|
|
198
|
+
* <p>The level of configured provisioned throughput for the
|
|
199
|
+
* table was exceeded. Consider increasing your provisioning level
|
|
200
|
+
* with the UpdateTable API.</p>
|
|
201
|
+
* <note>
|
|
202
|
+
* <p>This Message is received when provisioned throughput is
|
|
203
|
+
* exceeded is on a provisioned DynamoDB
|
|
204
|
+
* table.</p>
|
|
205
|
+
* </note>
|
|
206
|
+
* </li>
|
|
207
|
+
* <li>
|
|
208
|
+
* <p>The level of configured provisioned throughput for one or
|
|
209
|
+
* more global secondary indexes of the table was exceeded.
|
|
210
|
+
* Consider increasing your provisioning level for the
|
|
211
|
+
* under-provisioned global secondary indexes with the UpdateTable
|
|
212
|
+
* API.</p>
|
|
213
|
+
* <note>
|
|
214
|
+
* <p>This message is returned when provisioned throughput is
|
|
215
|
+
* exceeded is on a provisioned GSI.</p>
|
|
216
|
+
* </note>
|
|
217
|
+
* </li>
|
|
218
|
+
* </ul>
|
|
219
|
+
* </li>
|
|
220
|
+
* </ul>
|
|
221
|
+
* </li>
|
|
222
|
+
* <li>
|
|
223
|
+
* <p>Throttling Error:</p>
|
|
224
|
+
* <ul>
|
|
225
|
+
* <li>
|
|
226
|
+
* <p>Code: <code>ThrottlingError</code>
|
|
227
|
+
* </p>
|
|
228
|
+
* </li>
|
|
229
|
+
* <li>
|
|
230
|
+
* <p>Messages: </p>
|
|
231
|
+
* <ul>
|
|
232
|
+
* <li>
|
|
233
|
+
* <p>Throughput exceeds the current capacity of your table or
|
|
234
|
+
* index. DynamoDB is automatically scaling your table or
|
|
235
|
+
* index so please try again shortly. If exceptions persist, check
|
|
236
|
+
* if you have a hot key:
|
|
237
|
+
* https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html.</p>
|
|
238
|
+
* <note>
|
|
239
|
+
* <p>This message is returned when writes get throttled on an
|
|
240
|
+
* On-Demand table as DynamoDB is automatically
|
|
241
|
+
* scaling the table.</p>
|
|
242
|
+
* </note>
|
|
243
|
+
* </li>
|
|
244
|
+
* <li>
|
|
245
|
+
* <p>Throughput exceeds the current capacity for one or more
|
|
246
|
+
* global secondary indexes. DynamoDB is automatically
|
|
247
|
+
* scaling your index so please try again shortly.</p>
|
|
248
|
+
* <note>
|
|
249
|
+
* <p>This message is returned when writes get throttled on
|
|
250
|
+
* an On-Demand GSI as DynamoDB is automatically
|
|
251
|
+
* scaling the GSI.</p>
|
|
252
|
+
* </note>
|
|
253
|
+
* </li>
|
|
254
|
+
* </ul>
|
|
255
|
+
* </li>
|
|
256
|
+
* </ul>
|
|
257
|
+
* </li>
|
|
258
|
+
* <li>
|
|
259
|
+
* <p>Validation Error:</p>
|
|
260
|
+
* <ul>
|
|
261
|
+
* <li>
|
|
262
|
+
* <p>Code: <code>ValidationError</code>
|
|
263
|
+
* </p>
|
|
264
|
+
* </li>
|
|
265
|
+
* <li>
|
|
266
|
+
* <p>Messages: </p>
|
|
267
|
+
* <ul>
|
|
268
|
+
* <li>
|
|
269
|
+
* <p>One or more parameter values were invalid.</p>
|
|
270
|
+
* </li>
|
|
271
|
+
* <li>
|
|
272
|
+
* <p>The update expression attempted to update the secondary
|
|
273
|
+
* index key beyond allowed size limits.</p>
|
|
274
|
+
* </li>
|
|
275
|
+
* <li>
|
|
276
|
+
* <p>The update expression attempted to update the secondary
|
|
277
|
+
* index key to unsupported type.</p>
|
|
278
|
+
* </li>
|
|
279
|
+
* <li>
|
|
280
|
+
* <p>An operand in the update expression has an incorrect data
|
|
281
|
+
* type.</p>
|
|
282
|
+
* </li>
|
|
283
|
+
* <li>
|
|
284
|
+
* <p>Item size to update has exceeded the maximum allowed
|
|
285
|
+
* size.</p>
|
|
286
|
+
* </li>
|
|
287
|
+
* <li>
|
|
288
|
+
* <p>Number overflow. Attempting to store a number with
|
|
289
|
+
* magnitude larger than supported range.</p>
|
|
290
|
+
* </li>
|
|
291
|
+
* <li>
|
|
292
|
+
* <p>Type mismatch for attribute to update.</p>
|
|
293
|
+
* </li>
|
|
294
|
+
* <li>
|
|
295
|
+
* <p>Nesting Levels have exceeded supported limits.</p>
|
|
296
|
+
* </li>
|
|
297
|
+
* <li>
|
|
298
|
+
* <p>The document path provided in the update expression is
|
|
299
|
+
* invalid for update.</p>
|
|
300
|
+
* </li>
|
|
301
|
+
* <li>
|
|
302
|
+
* <p>The provided expression refers to an attribute that does
|
|
303
|
+
* not exist in the item.</p>
|
|
304
|
+
* </li>
|
|
305
|
+
* </ul>
|
|
306
|
+
* </li>
|
|
307
|
+
* </ul>
|
|
308
|
+
* </li>
|
|
309
|
+
* </ul>
|
|
310
|
+
*
|
|
311
|
+
*
|
|
58
312
|
*/
|
|
59
313
|
export declare class TransactGetItemsCommand extends $Command<TransactGetItemsCommandInput, TransactGetItemsCommandOutput, DynamoDBClientResolvedConfig> {
|
|
60
314
|
readonly input: TransactGetItemsCommandInput;
|
|
@@ -101,6 +101,329 @@ export interface TransactWriteItemsCommandOutput extends TransactWriteItemsOutpu
|
|
|
101
101
|
* @see {@link TransactWriteItemsCommandOutput} for command's `response` shape.
|
|
102
102
|
* @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
|
|
103
103
|
*
|
|
104
|
+
* @throws {@link IdempotentParameterMismatchException} (client fault)
|
|
105
|
+
* <p>DynamoDB rejected the request because you retried a request with a
|
|
106
|
+
* different payload but with an idempotent token that was already used.</p>
|
|
107
|
+
*
|
|
108
|
+
* @throws {@link InternalServerError} (server fault)
|
|
109
|
+
* <p>An error occurred on the server side.</p>
|
|
110
|
+
*
|
|
111
|
+
* @throws {@link InvalidEndpointException} (client fault)
|
|
112
|
+
*
|
|
113
|
+
* @throws {@link ProvisionedThroughputExceededException} (client fault)
|
|
114
|
+
* <p>Your request rate is too high. The Amazon Web Services SDKs for DynamoDB
|
|
115
|
+
* automatically retry requests that receive this exception. Your request is eventually
|
|
116
|
+
* successful, unless your retry queue is too large to finish. Reduce the frequency of
|
|
117
|
+
* requests and use exponential backoff. For more information, go to <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html#Programming.Errors.RetryAndBackoff">Error Retries and Exponential Backoff</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
|
|
118
|
+
*
|
|
119
|
+
* @throws {@link RequestLimitExceeded} (client fault)
|
|
120
|
+
* <p>Throughput exceeds the current throughput quota for your account. Please contact
|
|
121
|
+
* <a href="https://aws.amazon.com/support">Amazon Web Services Support</a> to request a
|
|
122
|
+
* quota increase.</p>
|
|
123
|
+
*
|
|
124
|
+
* @throws {@link ResourceNotFoundException} (client fault)
|
|
125
|
+
* <p>The operation tried to access a nonexistent table or index. The resource might not
|
|
126
|
+
* be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
|
|
127
|
+
*
|
|
128
|
+
* @throws {@link TransactionCanceledException} (client fault)
|
|
129
|
+
* <p>The entire transaction request was canceled.</p>
|
|
130
|
+
* <p>DynamoDB cancels a <code>TransactWriteItems</code> request under the following
|
|
131
|
+
* circumstances:</p>
|
|
132
|
+
* <ul>
|
|
133
|
+
* <li>
|
|
134
|
+
* <p>A condition in one of the condition expressions is not met.</p>
|
|
135
|
+
* </li>
|
|
136
|
+
* <li>
|
|
137
|
+
* <p>A table in the <code>TransactWriteItems</code> request is in a different
|
|
138
|
+
* account or region.</p>
|
|
139
|
+
* </li>
|
|
140
|
+
* <li>
|
|
141
|
+
* <p>More than one action in the <code>TransactWriteItems</code> operation
|
|
142
|
+
* targets the same item.</p>
|
|
143
|
+
* </li>
|
|
144
|
+
* <li>
|
|
145
|
+
* <p>There is insufficient provisioned capacity for the transaction to be
|
|
146
|
+
* completed.</p>
|
|
147
|
+
* </li>
|
|
148
|
+
* <li>
|
|
149
|
+
* <p>An item size becomes too large (larger than 400 KB), or a local secondary
|
|
150
|
+
* index (LSI) becomes too large, or a similar validation error occurs because of
|
|
151
|
+
* changes made by the transaction.</p>
|
|
152
|
+
* </li>
|
|
153
|
+
* <li>
|
|
154
|
+
* <p>There is a user error, such as an invalid data format.</p>
|
|
155
|
+
* </li>
|
|
156
|
+
* </ul>
|
|
157
|
+
* <p>DynamoDB cancels a <code>TransactGetItems</code> request under the
|
|
158
|
+
* following circumstances:</p>
|
|
159
|
+
* <ul>
|
|
160
|
+
* <li>
|
|
161
|
+
* <p>There is an ongoing <code>TransactGetItems</code> operation that conflicts
|
|
162
|
+
* with a concurrent <code>PutItem</code>, <code>UpdateItem</code>,
|
|
163
|
+
* <code>DeleteItem</code> or <code>TransactWriteItems</code> request. In this
|
|
164
|
+
* case the <code>TransactGetItems</code> operation fails with a
|
|
165
|
+
* <code>TransactionCanceledException</code>.</p>
|
|
166
|
+
* </li>
|
|
167
|
+
* <li>
|
|
168
|
+
* <p>A table in the <code>TransactGetItems</code> request is in a different
|
|
169
|
+
* account or region.</p>
|
|
170
|
+
* </li>
|
|
171
|
+
* <li>
|
|
172
|
+
* <p>There is insufficient provisioned capacity for the transaction to be
|
|
173
|
+
* completed.</p>
|
|
174
|
+
* </li>
|
|
175
|
+
* <li>
|
|
176
|
+
* <p>There is a user error, such as an invalid data format.</p>
|
|
177
|
+
* </li>
|
|
178
|
+
* </ul>
|
|
179
|
+
* <note>
|
|
180
|
+
* <p>If using Java, DynamoDB lists the cancellation reasons on the
|
|
181
|
+
* <code>CancellationReasons</code> property. This property is not set for other
|
|
182
|
+
* languages. Transaction cancellation reasons are ordered in the order of requested
|
|
183
|
+
* items, if an item has no error it will have <code>None</code> code and
|
|
184
|
+
* <code>Null</code> message.</p>
|
|
185
|
+
* </note>
|
|
186
|
+
* <p>Cancellation reason codes and possible error messages:</p>
|
|
187
|
+
* <ul>
|
|
188
|
+
* <li>
|
|
189
|
+
* <p>No Errors:</p>
|
|
190
|
+
* <ul>
|
|
191
|
+
* <li>
|
|
192
|
+
* <p>Code: <code>None</code>
|
|
193
|
+
* </p>
|
|
194
|
+
* </li>
|
|
195
|
+
* <li>
|
|
196
|
+
* <p>Message: <code>null</code>
|
|
197
|
+
* </p>
|
|
198
|
+
* </li>
|
|
199
|
+
* </ul>
|
|
200
|
+
* </li>
|
|
201
|
+
* <li>
|
|
202
|
+
* <p>Conditional Check Failed:</p>
|
|
203
|
+
* <ul>
|
|
204
|
+
* <li>
|
|
205
|
+
* <p>Code: <code>ConditionalCheckFailed</code>
|
|
206
|
+
* </p>
|
|
207
|
+
* </li>
|
|
208
|
+
* <li>
|
|
209
|
+
* <p>Message: The conditional request failed. </p>
|
|
210
|
+
* </li>
|
|
211
|
+
* </ul>
|
|
212
|
+
* </li>
|
|
213
|
+
* <li>
|
|
214
|
+
* <p>Item Collection Size Limit Exceeded:</p>
|
|
215
|
+
* <ul>
|
|
216
|
+
* <li>
|
|
217
|
+
* <p>Code: <code>ItemCollectionSizeLimitExceeded</code>
|
|
218
|
+
* </p>
|
|
219
|
+
* </li>
|
|
220
|
+
* <li>
|
|
221
|
+
* <p>Message: Collection size exceeded.</p>
|
|
222
|
+
* </li>
|
|
223
|
+
* </ul>
|
|
224
|
+
* </li>
|
|
225
|
+
* <li>
|
|
226
|
+
* <p>Transaction Conflict:</p>
|
|
227
|
+
* <ul>
|
|
228
|
+
* <li>
|
|
229
|
+
* <p>Code: <code>TransactionConflict</code>
|
|
230
|
+
* </p>
|
|
231
|
+
* </li>
|
|
232
|
+
* <li>
|
|
233
|
+
* <p>Message: Transaction is ongoing for the item.</p>
|
|
234
|
+
* </li>
|
|
235
|
+
* </ul>
|
|
236
|
+
* </li>
|
|
237
|
+
* <li>
|
|
238
|
+
* <p>Provisioned Throughput Exceeded:</p>
|
|
239
|
+
* <ul>
|
|
240
|
+
* <li>
|
|
241
|
+
* <p>Code: <code>ProvisionedThroughputExceeded</code>
|
|
242
|
+
* </p>
|
|
243
|
+
* </li>
|
|
244
|
+
* <li>
|
|
245
|
+
* <p>Messages:</p>
|
|
246
|
+
* <ul>
|
|
247
|
+
* <li>
|
|
248
|
+
* <p>The level of configured provisioned throughput for the
|
|
249
|
+
* table was exceeded. Consider increasing your provisioning level
|
|
250
|
+
* with the UpdateTable API.</p>
|
|
251
|
+
* <note>
|
|
252
|
+
* <p>This Message is received when provisioned throughput is
|
|
253
|
+
* exceeded is on a provisioned DynamoDB
|
|
254
|
+
* table.</p>
|
|
255
|
+
* </note>
|
|
256
|
+
* </li>
|
|
257
|
+
* <li>
|
|
258
|
+
* <p>The level of configured provisioned throughput for one or
|
|
259
|
+
* more global secondary indexes of the table was exceeded.
|
|
260
|
+
* Consider increasing your provisioning level for the
|
|
261
|
+
* under-provisioned global secondary indexes with the UpdateTable
|
|
262
|
+
* API.</p>
|
|
263
|
+
* <note>
|
|
264
|
+
* <p>This message is returned when provisioned throughput is
|
|
265
|
+
* exceeded is on a provisioned GSI.</p>
|
|
266
|
+
* </note>
|
|
267
|
+
* </li>
|
|
268
|
+
* </ul>
|
|
269
|
+
* </li>
|
|
270
|
+
* </ul>
|
|
271
|
+
* </li>
|
|
272
|
+
* <li>
|
|
273
|
+
* <p>Throttling Error:</p>
|
|
274
|
+
* <ul>
|
|
275
|
+
* <li>
|
|
276
|
+
* <p>Code: <code>ThrottlingError</code>
|
|
277
|
+
* </p>
|
|
278
|
+
* </li>
|
|
279
|
+
* <li>
|
|
280
|
+
* <p>Messages: </p>
|
|
281
|
+
* <ul>
|
|
282
|
+
* <li>
|
|
283
|
+
* <p>Throughput exceeds the current capacity of your table or
|
|
284
|
+
* index. DynamoDB is automatically scaling your table or
|
|
285
|
+
* index so please try again shortly. If exceptions persist, check
|
|
286
|
+
* if you have a hot key:
|
|
287
|
+
* https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html.</p>
|
|
288
|
+
* <note>
|
|
289
|
+
* <p>This message is returned when writes get throttled on an
|
|
290
|
+
* On-Demand table as DynamoDB is automatically
|
|
291
|
+
* scaling the table.</p>
|
|
292
|
+
* </note>
|
|
293
|
+
* </li>
|
|
294
|
+
* <li>
|
|
295
|
+
* <p>Throughput exceeds the current capacity for one or more
|
|
296
|
+
* global secondary indexes. DynamoDB is automatically
|
|
297
|
+
* scaling your index so please try again shortly.</p>
|
|
298
|
+
* <note>
|
|
299
|
+
* <p>This message is returned when writes get throttled on
|
|
300
|
+
* an On-Demand GSI as DynamoDB is automatically
|
|
301
|
+
* scaling the GSI.</p>
|
|
302
|
+
* </note>
|
|
303
|
+
* </li>
|
|
304
|
+
* </ul>
|
|
305
|
+
* </li>
|
|
306
|
+
* </ul>
|
|
307
|
+
* </li>
|
|
308
|
+
* <li>
|
|
309
|
+
* <p>Validation Error:</p>
|
|
310
|
+
* <ul>
|
|
311
|
+
* <li>
|
|
312
|
+
* <p>Code: <code>ValidationError</code>
|
|
313
|
+
* </p>
|
|
314
|
+
* </li>
|
|
315
|
+
* <li>
|
|
316
|
+
* <p>Messages: </p>
|
|
317
|
+
* <ul>
|
|
318
|
+
* <li>
|
|
319
|
+
* <p>One or more parameter values were invalid.</p>
|
|
320
|
+
* </li>
|
|
321
|
+
* <li>
|
|
322
|
+
* <p>The update expression attempted to update the secondary
|
|
323
|
+
* index key beyond allowed size limits.</p>
|
|
324
|
+
* </li>
|
|
325
|
+
* <li>
|
|
326
|
+
* <p>The update expression attempted to update the secondary
|
|
327
|
+
* index key to unsupported type.</p>
|
|
328
|
+
* </li>
|
|
329
|
+
* <li>
|
|
330
|
+
* <p>An operand in the update expression has an incorrect data
|
|
331
|
+
* type.</p>
|
|
332
|
+
* </li>
|
|
333
|
+
* <li>
|
|
334
|
+
* <p>Item size to update has exceeded the maximum allowed
|
|
335
|
+
* size.</p>
|
|
336
|
+
* </li>
|
|
337
|
+
* <li>
|
|
338
|
+
* <p>Number overflow. Attempting to store a number with
|
|
339
|
+
* magnitude larger than supported range.</p>
|
|
340
|
+
* </li>
|
|
341
|
+
* <li>
|
|
342
|
+
* <p>Type mismatch for attribute to update.</p>
|
|
343
|
+
* </li>
|
|
344
|
+
* <li>
|
|
345
|
+
* <p>Nesting Levels have exceeded supported limits.</p>
|
|
346
|
+
* </li>
|
|
347
|
+
* <li>
|
|
348
|
+
* <p>The document path provided in the update expression is
|
|
349
|
+
* invalid for update.</p>
|
|
350
|
+
* </li>
|
|
351
|
+
* <li>
|
|
352
|
+
* <p>The provided expression refers to an attribute that does
|
|
353
|
+
* not exist in the item.</p>
|
|
354
|
+
* </li>
|
|
355
|
+
* </ul>
|
|
356
|
+
* </li>
|
|
357
|
+
* </ul>
|
|
358
|
+
* </li>
|
|
359
|
+
* </ul>
|
|
360
|
+
*
|
|
361
|
+
* @throws {@link TransactionInProgressException} (client fault)
|
|
362
|
+
* <p>The transaction with the given request token is already in progress.</p>
|
|
363
|
+
* <p>
|
|
364
|
+
* Recommended Settings
|
|
365
|
+
* </p>
|
|
366
|
+
* <note>
|
|
367
|
+
* <p>
|
|
368
|
+
* This is a general recommendation for handling the <code>TransactionInProgressException</code>. These settings help
|
|
369
|
+
* ensure that the client retries will trigger completion of the ongoing <code>TransactWriteItems</code> request.
|
|
370
|
+
* </p>
|
|
371
|
+
* </note>
|
|
372
|
+
* <ul>
|
|
373
|
+
* <li>
|
|
374
|
+
* <p>
|
|
375
|
+
* Set <code>clientExecutionTimeout</code> to a value that allows at least one retry to be processed after 5
|
|
376
|
+
* seconds have elapsed since the first attempt for the <code>TransactWriteItems</code> operation.
|
|
377
|
+
* </p>
|
|
378
|
+
* </li>
|
|
379
|
+
* <li>
|
|
380
|
+
* <p>
|
|
381
|
+
* Set <code>socketTimeout</code> to a value a little lower than the <code>requestTimeout</code> setting.
|
|
382
|
+
* </p>
|
|
383
|
+
* </li>
|
|
384
|
+
* <li>
|
|
385
|
+
* <p>
|
|
386
|
+
* <code>requestTimeout</code> should be set based on the time taken for the individual retries of a single
|
|
387
|
+
* HTTP request for your use case, but setting it to 1 second or higher should work well to reduce chances of
|
|
388
|
+
* retries and <code>TransactionInProgressException</code> errors.
|
|
389
|
+
* </p>
|
|
390
|
+
* </li>
|
|
391
|
+
* <li>
|
|
392
|
+
* <p>
|
|
393
|
+
* Use exponential backoff when retrying and tune backoff if needed.
|
|
394
|
+
* </p>
|
|
395
|
+
* </li>
|
|
396
|
+
* </ul>
|
|
397
|
+
* <p>
|
|
398
|
+
* Assuming <a href="https://github.com/aws/aws-sdk-java/blob/fd409dee8ae23fb8953e0bb4dbde65536a7e0514/aws-java-sdk-core/src/main/java/com/amazonaws/retry/PredefinedRetryPolicies.java#L97">default retry policy</a>,
|
|
399
|
+
* example timeout settings based on the guidelines above are as follows:
|
|
400
|
+
* </p>
|
|
401
|
+
* <p>Example timeline:</p>
|
|
402
|
+
* <ul>
|
|
403
|
+
* <li>
|
|
404
|
+
* <p>0-1000 first attempt</p>
|
|
405
|
+
* </li>
|
|
406
|
+
* <li>
|
|
407
|
+
* <p>1000-1500 first sleep/delay (default retry policy uses 500 ms as base delay for 4xx errors)</p>
|
|
408
|
+
* </li>
|
|
409
|
+
* <li>
|
|
410
|
+
* <p>1500-2500 second attempt</p>
|
|
411
|
+
* </li>
|
|
412
|
+
* <li>
|
|
413
|
+
* <p>2500-3500 second sleep/delay (500 * 2, exponential backoff)</p>
|
|
414
|
+
* </li>
|
|
415
|
+
* <li>
|
|
416
|
+
* <p>3500-4500 third attempt</p>
|
|
417
|
+
* </li>
|
|
418
|
+
* <li>
|
|
419
|
+
* <p>4500-6500 third sleep/delay (500 * 2^2)</p>
|
|
420
|
+
* </li>
|
|
421
|
+
* <li>
|
|
422
|
+
* <p>6500-7500 fourth attempt (this can trigger inline recovery since 5 seconds have elapsed since the first attempt reached TC)</p>
|
|
423
|
+
* </li>
|
|
424
|
+
* </ul>
|
|
425
|
+
*
|
|
426
|
+
*
|
|
104
427
|
*/
|
|
105
428
|
export declare class TransactWriteItemsCommand extends $Command<TransactWriteItemsCommandInput, TransactWriteItemsCommandOutput, DynamoDBClientResolvedConfig> {
|
|
106
429
|
readonly input: TransactWriteItemsCommandInput;
|
|
@@ -32,6 +32,34 @@ export interface UntagResourceCommandOutput extends __MetadataBearer {
|
|
|
32
32
|
* @see {@link UntagResourceCommandOutput} for command's `response` shape.
|
|
33
33
|
* @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
|
|
34
34
|
*
|
|
35
|
+
* @throws {@link InternalServerError} (server fault)
|
|
36
|
+
* <p>An error occurred on the server side.</p>
|
|
37
|
+
*
|
|
38
|
+
* @throws {@link InvalidEndpointException} (client fault)
|
|
39
|
+
*
|
|
40
|
+
* @throws {@link LimitExceededException} (client fault)
|
|
41
|
+
* <p>There is no limit to the number of daily on-demand backups that can be taken. </p>
|
|
42
|
+
* <p>For most purposes, up to 500 simultaneous table operations are allowed per account. These operations
|
|
43
|
+
* include <code>CreateTable</code>, <code>UpdateTable</code>,
|
|
44
|
+
* <code>DeleteTable</code>,<code>UpdateTimeToLive</code>,
|
|
45
|
+
* <code>RestoreTableFromBackup</code>, and <code>RestoreTableToPointInTime</code>. </p>
|
|
46
|
+
* <p>When you are creating a table with one or more secondary
|
|
47
|
+
* indexes, you can have up to 250 such requests running at a time. However, if the table or
|
|
48
|
+
* index specifications are complex, then DynamoDB might temporarily reduce the number
|
|
49
|
+
* of concurrent operations.</p>
|
|
50
|
+
* <p>When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.</p>
|
|
51
|
+
* <p>There is a soft account quota of 2,500 tables.</p>
|
|
52
|
+
*
|
|
53
|
+
* @throws {@link ResourceInUseException} (client fault)
|
|
54
|
+
* <p>The operation conflicts with the resource's availability. For example, you
|
|
55
|
+
* attempted to recreate an existing table, or tried to delete a table currently in the
|
|
56
|
+
* <code>CREATING</code> state.</p>
|
|
57
|
+
*
|
|
58
|
+
* @throws {@link ResourceNotFoundException} (client fault)
|
|
59
|
+
* <p>The operation tried to access a nonexistent table or index. The resource might not
|
|
60
|
+
* be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
|
|
61
|
+
*
|
|
62
|
+
*
|
|
35
63
|
*/
|
|
36
64
|
export declare class UntagResourceCommand extends $Command<UntagResourceCommandInput, UntagResourceCommandOutput, DynamoDBClientResolvedConfig> {
|
|
37
65
|
readonly input: UntagResourceCommandInput;
|
|
@@ -40,6 +40,19 @@ export interface UpdateContinuousBackupsCommandOutput extends UpdateContinuousBa
|
|
|
40
40
|
* @see {@link UpdateContinuousBackupsCommandOutput} for command's `response` shape.
|
|
41
41
|
* @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
|
|
42
42
|
*
|
|
43
|
+
* @throws {@link ContinuousBackupsUnavailableException} (client fault)
|
|
44
|
+
* <p>Backups have not yet been enabled for this table.</p>
|
|
45
|
+
*
|
|
46
|
+
* @throws {@link InternalServerError} (server fault)
|
|
47
|
+
* <p>An error occurred on the server side.</p>
|
|
48
|
+
*
|
|
49
|
+
* @throws {@link InvalidEndpointException} (client fault)
|
|
50
|
+
*
|
|
51
|
+
* @throws {@link TableNotFoundException} (client fault)
|
|
52
|
+
* <p>A source table with the name <code>TableName</code> does not currently exist within
|
|
53
|
+
* the subscriber's account or the subscriber is operating in the wrong Amazon Web Services Region.</p>
|
|
54
|
+
*
|
|
55
|
+
*
|
|
43
56
|
*/
|
|
44
57
|
export declare class UpdateContinuousBackupsCommand extends $Command<UpdateContinuousBackupsCommandInput, UpdateContinuousBackupsCommandOutput, DynamoDBClientResolvedConfig> {
|
|
45
58
|
readonly input: UpdateContinuousBackupsCommandInput;
|
|
@@ -35,6 +35,14 @@ export interface UpdateContributorInsightsCommandOutput extends UpdateContributo
|
|
|
35
35
|
* @see {@link UpdateContributorInsightsCommandOutput} for command's `response` shape.
|
|
36
36
|
* @see {@link DynamoDBClientResolvedConfig | config} for DynamoDBClient's `config` shape.
|
|
37
37
|
*
|
|
38
|
+
* @throws {@link InternalServerError} (server fault)
|
|
39
|
+
* <p>An error occurred on the server side.</p>
|
|
40
|
+
*
|
|
41
|
+
* @throws {@link ResourceNotFoundException} (client fault)
|
|
42
|
+
* <p>The operation tried to access a nonexistent table or index. The resource might not
|
|
43
|
+
* be specified correctly, or its status might not be <code>ACTIVE</code>.</p>
|
|
44
|
+
*
|
|
45
|
+
*
|
|
38
46
|
*/
|
|
39
47
|
export declare class UpdateContributorInsightsCommand extends $Command<UpdateContributorInsightsCommandInput, UpdateContributorInsightsCommandOutput, DynamoDBClientResolvedConfig> {
|
|
40
48
|
readonly input: UpdateContributorInsightsCommandInput;
|