[jira] [Work logged] (BEAM-8542) Add async write to AWS SNS IO & remove retry logic

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-8542?focusedWorklogId=429385&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-429385 ]

ASF GitHub Bot logged work on BEAM-8542:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/May/20 06:34
            Start Date: 01/May/20 06:34
    Worklog Time Spent: 10m 
      Work Description: Akshay-Iyangar commented on pull request #10078:
URL: https://github.com/apache/beam/pull/10078#issuecomment-622269940


   @aromanenko-dev - addressed the feedback. thanks


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 429385)
    Time Spent: 9h 20m  (was: 9h 10m)

> Add async write to AWS SNS IO & remove retry logic
> --------------------------------------------------
>
>                 Key: BEAM-8542
>                 URL: https://issues.apache.org/jira/browse/BEAM-8542
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-aws
>            Reporter: Ajo Thomas
>            Assignee: Ajo Thomas
>            Priority: Major
>          Time Spent: 9h 20m
>  Remaining Estimate: 0h
>
> - While working with SNS IO for one of my work-related projects, I found that the IO uses synchronous publishes during writes. I had a simple mock pipeline where I was reading from a kinesis stream and publishing it to SNS using Beam's SNS IO. For comparison, I also had a lamdba which did the same using asynchronous publishes but was about 5x faster. Changing the SNS IO to use async publishes would improve publish latencies.
>  - SNS IO also has some retry logic which isn't required as SNS clients can handle retries. The retry logic in the SNS client is user-configurable and therefore, an explicit retry logic in SNS IO is not required
> I have a working version of the IO with these changes, will create a PR linking this ticket to it once I get some feedback here.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)