put_item
¶
put_item(
table_name: TableArn,
item: PutItemInputAttributeMap,
*,
config_overrides: Optional[DynamoDBClientConfig] = None,
expected: Optional[ExpectedAttributeMap] = None,
return_values: Optional[ReturnValue] = None,
return_consumed_capacity: Optional[ReturnConsumedCapacity] = None,
return_item_collection_metrics: Optional[ReturnItemCollectionMetrics] = None,
conditional_operator: Optional[ConditionalOperator] = None,
condition_expression: Optional[ConditionExpression] = None,
expression_attribute_names: Optional[ExpressionAttributeNameMap] = None,
expression_attribute_values: Optional[ExpressionAttributeValueMap] = None,
return_values_on_condition_check_failure: Optional[
ReturnValuesOnConditionCheckFailure
] = None,
) -> PutItemOutput
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 ReturnValues parameter.
When you add an item, the primary key attributes are the only required attributes.
Empty String and Binary attribute values are allowed. Attribute values of type String and Binary must have a length greater than zero if the attribute is used as a key attribute for a table or index. Set type attributes cannot be empty.
Invalid Requests with empty values will be rejected with a ValidationException exception.
To prevent a new item from replacing an existing item, use a conditional expression that contains the attribute_not_exists function with the name of the attribute being used as the partition key for the table. Since every record must contain that attribute, the attribute_not_exists function will only succeed if no matching item exists.
To determine whether PutItem overwrote an existing item, use ReturnValues set to ALL_OLD. If the response includes the Attributes element, an existing item was overwritten.
For more information about PutItem, see Working with Items in the Amazon DynamoDB Developer Guide.
Parameters:
-
table_name(TableArn) –The name of the table to contain the item. You can also provide the Amazon Resource Name (ARN) of the table in this parameter.
-
item(PutItemInputAttributeMap) –A map of attribute name/value pairs, one for each attribute. Only the primary key attributes are required; you can optionally provide other attribute name-value pairs for the item.
You must provide all of the attributes for the primary key. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide both values for both the partition key and the sort key.
If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition.
If the table has vector indexes, the following validations apply to write operations. A violation of any of these constraints results in a
ValidationException:-
The vector attribute must be a list of numbers with dimensions matching the index configuration.
-
Vector values must fit in 32-bit IEEE-754 floating point format (f32).
-
Partition key and inline filter attributes defined in the search schema must have data types matching the index schema definition.
Empty String and Binary attribute values are allowed. Attribute values of type String and Binary must have a length greater than zero if the attribute is used as a key attribute for a table or index.
For more information about primary keys, see Primary Key in the Amazon DynamoDB Developer Guide.
Each element in the
Itemmap is anAttributeValueobject. -
-
expected(Optional[ExpectedAttributeMap], default:None) –This is a legacy parameter. Use
ConditionExpressioninstead. For more information, see Expected in the Amazon DynamoDB Developer Guide. -
return_values(Optional[ReturnValue], default:None) –Use
ReturnValuesif you want to get the item attributes as they appeared before they were updated with thePutItemrequest. ForPutItem, the valid values are:-
NONE- IfReturnValuesis not specified, or if its value isNONE, then nothing is returned. (This setting is the default forReturnValues.) -
ALL_OLD- IfPutItemoverwrote an attribute name-value pair, then the content of the old item is returned.
The values returned are strongly consistent.
There is no additional cost associated with requesting a return value aside from the small network and processing overhead of receiving a larger response. No read capacity units are consumed.
The
ReturnValuesparameter is used by several DynamoDB operations; however,PutItemdoes not recognize any values other thanNONEorALL_OLD. -
-
return_item_collection_metrics(Optional[ReturnItemCollectionMetrics], default:None) –Determines whether item collection metrics are returned. If set to
SIZE, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set toNONE(the default), no statistics are returned. -
conditional_operator(Optional[ConditionalOperator], default:None) –This is a legacy parameter. Use
ConditionExpressioninstead. For more information, see ConditionalOperator in the Amazon DynamoDB Developer Guide. -
condition_expression(Optional[ConditionExpression], default:None) –A condition that must be satisfied in order for a conditional
PutItemoperation to succeed.An expression can contain any of the following:
-
Functions:
attribute_exists | attribute_not_exists | attribute_type | contains | begins_with | sizeThese function names are case-sensitive.
-
Comparison operators:
= | <> | < | > | <= | >= | BETWEEN | IN -
Logical operators:
AND | OR | NOT
For more information on condition expressions, see Condition Expressions in the Amazon DynamoDB Developer Guide.
-
-
expression_attribute_names(Optional[ExpressionAttributeNameMap], default:None) –One or more substitution tokens for attribute names in an expression. The following are some use cases for using
ExpressionAttributeNames:-
To access an attribute whose name conflicts with a DynamoDB reserved word.
-
To create a placeholder for repeating occurrences of an attribute name in an expression.
-
To prevent special characters in an attribute name from being misinterpreted in an expression.
Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name:
-
Percentile
The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for
ExpressionAttributeNames:-
{"#P":"Percentile"}
You could then use this substitution in an expression, as in this example:
-
#P = :val
Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime.
For more information on expression attribute names, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
-
-
expression_attribute_values(Optional[ExpressionAttributeValueMap], default:None) –One or more values that can be substituted in an expression.
Use the : (colon) character in an expression to dereference an attribute value. For example, suppose that you wanted to check whether the value of the ProductStatus attribute was one of the following:
Available | Backordered | DiscontinuedYou would first need to specify
ExpressionAttributeValuesas follows:{ ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} }You could then use these values in an expression, such as this:
ProductStatus IN (:avail, :back, :disc)For more information on expression attribute values, see Condition Expressions in the Amazon DynamoDB Developer Guide.
-
return_values_on_condition_check_failure(Optional[ReturnValuesOnConditionCheckFailure], default:None) –An optional parameter that returns the item attributes for a
PutItemoperation that failed a condition check.There is no additional cost associated with requesting a return value aside from the small network and processing overhead of receiving a larger response. No read capacity units are consumed.
Raises:
-
ConditionalCheckFailedException–A condition specified in the operation failed to be evaluated.
-
InternalServerError–An error occurred on the server side.
-
ItemCollectionSizeLimitExceededException–An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.
-
ProvisionedThroughputExceededException–The request was denied due to request throttling. For detailed information about why the request was throttled and the ARN of the impacted resource, find the ThrottlingReason field in the returned exception. The Amazon Web Services SDKs for DynamoDB automatically retry requests that receive this exception. Your request is eventually successful, unless your retry queue is too large to finish. Reduce the frequency of requests and use exponential backoff. For more information, go to Error Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
-
ReplicatedWriteConflictException–The request was rejected because one or more items in the request are being modified by a request in another Region.
-
RequestLimitExceeded–Throughput exceeds the current throughput quota for your account. For detailed information about why the request was throttled and the ARN of the impacted resource, find the ThrottlingReason field in the returned exception. Contact Amazon Web Services Support to request a quota increase.
-
ResourceNotFoundException–The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be
ACTIVE. -
ThrottlingException–The request was denied due to request throttling. For detailed information about why the request was throttled and the ARN of the impacted resource, find the ThrottlingReason field in the returned exception.
-
TransactionConflictException–Operation was rejected because there is an ongoing transaction for the item.
-
UnknownServiceError–The service returned an error code this client does not model.
Examples:
To add an item to a table This example adds a new item to the Music table.
>>> client.put_item(table_name='Music', item={'AlbumTitle': {'S': 'Somewhat Famous'}, 'SongTitle': {'S': 'Call Me Today'}, 'Artist': {'S': 'No One You Know'}}, return_consumed_capacity='TOTAL')
Source code in docs_src/capo_dynamodb/_services/dynamo_db.py
2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 | |