Read and Write data to DynamoDB
Write data
PutItem
1 2 3 4 5 6 |
|
--return-consumed-capacity determines the level of detail about either provisioned or on-demand throughput consumption that is returned in the response:
- INDEXES - The response includes the aggregate ConsumedCapacity for the operation, together with ConsumedCapacity for each table and secondary index that was accessed. Note that some operations, such as GetItem and BatchGetItem, do not access any indexes at all. In these cases, specifying INDEXES will only return ConsumedCapacity information for table(s).
- TOTAL - The response includes only the aggregate ConsumedCapacity for the operation.
- NONE - No ConsumedCapacity details are included in the response.
Note: If the primary key matches with a primary key of an item already present, the new item will REPLACE the old item.
BatchWriteItem
1 2 3 4 5 6 7 8 9 10 11 12 13 |
|
1 2 3 4 |
|
Read data
DynamoDB offers two ways to access information stored: Query and Scan.
Query
If our table doesn’t have a sort key, i.e the partition key that uniquely identifies every item in the table, we can only query one item at a time. We need to specify the partition key to query each item.
If the table also has a sort key, we can query multiple items by using a range-over-sort key. To query multiple items, we need to specify the partition key and a range-over-sort key. All items you want to query should be from the same partition. All the items from the given partition, that belong to the given range, are returned in a sorted order.
1 2 3 4 5 6 7 8 9 10 |
|
Amazon DynamoDB returns all the item attributes by default. To get only some, rather than all of the attributes, use a projection expression
.
Scan
Scan reads every item in a table, which can be inefficient and costly for large datasets. You can fetch a maximum of 1 MB of data in one go and you can also apply filters to refine the items you get, all while scanning
1 2 3 4 5 6 7 |
|