You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/27 11:00:00 UTC
[jira] [Work logged] (BEAM-13416) SqsIO.write input / construction of Sqs request
[ https://issues.apache.org/jira/browse/BEAM-13416?focusedWorklogId=762798&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-762798 ]
ASF GitHub Bot logged work on BEAM-13416:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Apr/22 10:59
Start Date: 27/Apr/22 10:59
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on PR #16947:
URL: https://github.com/apache/beam/pull/16947#issuecomment-1110863740
Ping. What is a state of this PR? What are the next steps?
Issue Time Tracking
-------------------
Worklog Id: (was: 762798)
Time Spent: 4h 50m (was: 4h 40m)
> SqsIO.write input / construction of Sqs request
> -----------------------------------------------
>
> Key: BEAM-13416
> URL: https://issues.apache.org/jira/browse/BEAM-13416
> Project: Beam
> Issue Type: Improvement
> Components: io-java-aws
> Reporter: Moritz Mack
> Priority: P2
> Labels: aws, aws-sdk-v2, sqs
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> 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.7#820007)