Configure tFixedFlowInput to load the sample data in the data flow and configure tDynamoDBOutput to write this data in a DynamoDB table.
About this task
Procedure
Double-click tFixedFlowInput in its
Component view.
Example
Click the ... button next to Edit
schema to open the schema editor.
Example
Click the + button twice to add two rows, each
representing a column of the sample data, and in the
Column column, name these columns to
DeliveryId and EventPayload,
respectively.
On the row for the DeliveryId column, select the check
box in the Key column to use this
DeliveryID column as the partition key column of the
DynamoDB table to be used. A DynamoDB table requires a partition key
column.
Click OK to validate these changes and once prompted,
accept the propagation of the schema to the connected component,
tDynamoDBOutput.
In the Mode area, select the Use Inline
content radio box and enter the sample data in the field that is
displayed:
Double-click tDynamoDBOutput to open its
Component view.
Example
Click the ... button next to Edit schema to open the schema editor. This
component should have retrieved the schema from
tFixedFlowInput.
Example
In the DB Type column, select
JSON for the EventPayload
column, as this is the column in which the JSON documents are stored.
In the Access key and Secret key
fields, enter the credentials of the AWS account to be used to access your
DynamoDB database.
From the Region drop-down list, select the AWS region to
be used. If you do not know which region to select, ask the administrator of
your AWS system for more information.
From the Action on table drop-down list, select
Drop table is exists and create.
From the Action on data drop-down list, select
Insert.
In the Table name field, enter the name to be used for
the DynamoDB table to be created.
In the Partition Key field, enter the name of the column
to be used to provide parition keys. In this example, it is
DeliveryId.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!