Open ashoktelukuntla opened 1 year ago
Support FIFO queues would be good. And it would require that we allow users to configure both the de-duplication Id and the message group Id. These should be configurable either as string literals or as variables within an event. The de-duplication Id can also be a random string by default, but users must be able to configure this.
Here is an example. Say my events have a couple of properties - a "type" and an "id". I want any messages of the same type to be in order. So I'd like the type value for each event to define the message group Id. Then my deduplication Id is set to the "id" key.
sink:
- sns:
topic_name: "mytopic"
message_deduplication_id: "${/id}"
message_group_id: "${/type}"
The ${/id}
syntax tells Data Prepper to get the value of the key named "id".
It also would be good to consider using the PublishBatch API to reduce the number of API calls. This API can accept up to 10 messages in a single call.
Perhaps add a new parameter: batch_size
which takes an integer value. It must be restricted to be between 1-10 inclusive.
sink:
- sns:
topic_name: my_topic
batch_size: 10
Is your feature request related to a problem? Please describe.
Pipeline users want to send message to an Amazon Simple Notification Service (SNS) topic.
Describe the solution you'd like
Create a new sink in Data Prepper which outputs data to topic using codec
Additional context