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/13 09:44:00 UTC

[jira] [Assigned] (BEAM-13653) Improved handling of topicArn in SnsIO.write

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

Moritz Mack reassigned BEAM-13653:
----------------------------------

    Assignee: Moritz Mack

> Improved handling of topicArn in SnsIO.write 
> ---------------------------------------------
>
>                 Key: BEAM-13653
>                 URL: https://issues.apache.org/jira/browse/BEAM-13653
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-aws
>            Reporter: Moritz Mack
>            Assignee: Moritz Mack
>            Priority: P2
>              Labels: aws, aws-sdk-v2
>
> Usage of SnsIO.write is rather unintuitive at the moment.
> topicArn is a required configuration and during expansion the existence of the topic is validated.
> However, the user also has to provide a function to build an SNS publish request. The topicArn for that publish request has to be set as well, but can be different from the one configured and validated in the writer. 
> This is confusing and makes any validation pointless.
> Also, when validating the SNS client instance is not closed.



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