[
https://issues.apache.org/jira/browse/BEAM-8542?focusedWorklogId=392984&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-392984
]
ASF GitHub Bot logged work on BEAM-8542:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Feb/20 21:45
Start Date: 25/Feb/20 21:45
Worklog Time Spent: 10m
Work Description: Akshay-Iyangar commented on issue #10078: [BEAM-8542]
Change write to async in AWS SNS IO & remove retry logic
URL: https://github.com/apache/beam/pull/10078#issuecomment-591086092
@ajothomas, @aromanenko-dev can you'll have a look?
Changes made got rid of the `WrappedSnsResponse` to send the exception back
to the client. An exception with AWS SNS will should actually throw an
exception.
For Response from the SNS client. I'm just returning the `requestElement,
statusText and statusCode`
to the users so they can determine how they want to handle the responses at
their side.
L
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 392984)
Time Spent: 5h 10m (was: 5h)
> 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: 5h 10m
> 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)
