You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Moritz Mack (Jira)" <ji...@apache.org> on 2022/01/12 14:31:00 UTC

[jira] [Updated] (BEAM-13416) SqsIO.write input / construction of Sqs request

     [ https://issues.apache.org/jira/browse/BEAM-13416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Moritz Mack updated BEAM-13416:
-------------------------------
    Summary: SqsIO.write input / construction of Sqs request  (was: SqsIO.write)

> SqsIO.write input / construction of Sqs request
> -----------------------------------------------
>
>                 Key: BEAM-13416
>                 URL: https://issues.apache.org/jira/browse/BEAM-13416
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-aws
>            Reporter: Moritz Mack
>            Priority: P2
>              Labels: aws, aws-sdk-v2, sqs
>
> SqsIO.write should support arbitrary types T and be implemented in terms of a mapper function that converts T into an AWS request.
> The current implementation of write as {{PTransform<PCollection<SendMessageRequest>, PDone>}} is a rather poor choice. It may requires an additional unnecessary serialization & deserialisation round. But even worse, the current {{SendMessageRequestCoder}} does not support any advanced configuration beyond queueUrl and messageBody and will silently drop it without even warning the user.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)