You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2023/04/12 13:00:50 UTC
[camel-kamelets] 01/02: DynamoDB Sink Kamelet: Improved description for put, update and delete item operation
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch ddb-sink
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit a9336798c8d11b88c19c619c7be798ddeefdee95
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Wed Apr 12 14:52:06 2023 +0200
DynamoDB Sink Kamelet: Improved description for put, update and delete item operation
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
kamelets/aws-ddb-sink.kamelet.yaml | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/kamelets/aws-ddb-sink.kamelet.yaml b/kamelets/aws-ddb-sink.kamelet.yaml
index 0899aba3..b930793d 100644
--- a/kamelets/aws-ddb-sink.kamelet.yaml
+++ b/kamelets/aws-ddb-sink.kamelet.yaml
@@ -38,7 +38,17 @@ spec:
If you use the default credentials provider, the DynamoDB client loads the credentials through this provider and doesn't use the basic authentication method.
- This Kamelet expects a JSON-formatted body and it must include the primary key values that define the DynamoDB item. The mapping between the JSON fields and table attribute values is done by key. For example, for '{"username":"oscerd", "city":"Rome"}' input, the Kamelet inserts or update an item in the specified AWS DynamoDB table and sets the values for the 'username' and 'city' attributes.
+ This Kamelet expects a JSON-formatted body and it must include the primary key values that define the DynamoDB item. The mapping between the JSON fields and table attribute values is done by key. For example, for '{"username":"oscerd", "city":"Rome"}' input, the Kamelet inserts or update an item in the specified AWS DynamoDB table and sets the values for the 'username' and 'city' attributes.
+
+ For PutItem operation the Json body defines all item attributes.
+ For DeleteItem operation the Json body defines only the primary key attributes that identify the item to delete.
+ For UpdateItem operation the Json body defines both key attributes to identify the item to be updated and all item attributes tht get updated on the item.
+
+ The given Json body can use "key" and "item" as top level properties. Both define a Json object that will be mapped to respective attribute value maps
+ {
+ "key": {},
+ "item": {}
+ }
required:
- table
- region