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:01:07 UTC

[camel-kamelets] branch 0.9.x-ddb-sink created (now 74dd5700)

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a change to branch 0.9.x-ddb-sink
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git


      at 74dd5700 Regen

This branch includes the following new commits:

     new 819900b9 DynamoDB Sink Kamelet: Improved description for put, update and delete item operation
     new 74dd5700 Regen

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[camel-kamelets] 02/02: Regen

Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch 0.9.x-ddb-sink
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git

commit 74dd57009a8591fa52adb6fcc8ad9906c7000878
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Wed Apr 12 14:53:41 2023 +0200

    Regen
    
    Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
 docs/modules/ROOT/nav.adoc                                     |  1 +
 .../src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml      | 10 ++++++++++
 .../src/main/resources/kamelets/telegram-source.kamelet.yaml   |  2 +-
 3 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
index 6fc66804..b0b79ec0 100644
--- a/docs/modules/ROOT/nav.adoc
+++ b/docs/modules/ROOT/nav.adoc
@@ -113,6 +113,7 @@
 * xref:json-schema-validator-action.adoc[]
 * xref:json-serialize-action.adoc[]
 * xref:jsonata-action.adoc[]
+* xref:kafka-aggregate-source.adoc[]
 * xref:kafka-manual-commit-action.adoc[]
 * xref:kafka-not-secured-sink.adoc[]
 * xref:kafka-not-secured-source.adoc[]
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml
index 3486816e..aa8798d1 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml
@@ -38,6 +38,16 @@ 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. 
+      
+      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
diff --git a/library/camel-kamelets/src/main/resources/kamelets/telegram-source.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/telegram-source.kamelet.yaml
index 9b625b90..fbc896ef 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/telegram-source.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/telegram-source.kamelet.yaml
@@ -44,7 +44,7 @@ spec:
     properties:
       authorizationToken:
         title: Token
-        description: "The token to access your bot on Telegram. You you can obtain it from the Telegram @botfather."
+        description: "The token to access your bot on Telegram. You can obtain it from the Telegram @botfather."
         type: string
         format: password
         x-descriptors:


[camel-kamelets] 01/02: DynamoDB Sink Kamelet: Improved description for put, update and delete item operation

Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch 0.9.x-ddb-sink
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git

commit 819900b96f2f0804e0b5b099daea272221d31f1f
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 | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/kamelets/aws-ddb-sink.kamelet.yaml b/kamelets/aws-ddb-sink.kamelet.yaml
index 3486816e..aa8798d1 100644
--- a/kamelets/aws-ddb-sink.kamelet.yaml
+++ b/kamelets/aws-ddb-sink.kamelet.yaml
@@ -38,6 +38,16 @@ 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. 
+      
+      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