[
https://issues.apache.org/jira/browse/BEAM-8374?focusedWorklogId=327156&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-327156
]
ASF GitHub Bot logged work on BEAM-8374:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Oct/19 00:02
Start Date: 12/Oct/19 00:02
Worklog Time Spent: 10m
Work Description: jfarr commented on issue #9758: [BEAM-8374] Fixes bug
in SnsIO PublishResultCoder
URL: https://github.com/apache/beam/pull/9758#issuecomment-541260123
> Note that this is a breaking change to any Dataflow streaming pipelines
using the PublishResult.
@lukecwik Thanks for the feedback. I did not realize that, I'm very new to
Beam. What do you suggest would be the best way to deal with that?
----------------------------------------------------------------
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: 327156)
Time Spent: 40m (was: 0.5h)
> PublishResult returned by SnsIO is missing sdkResponseMetadata and
> sdkHttpMetadata
> ----------------------------------------------------------------------------------
>
> Key: BEAM-8374
> URL: https://issues.apache.org/jira/browse/BEAM-8374
> Project: Beam
> Issue Type: Bug
> Components: io-java-aws
> Affects Versions: 2.13.0, 2.14.0, 2.15.0
> Reporter: Jonothan Farr
> Assignee: Jonothan Farr
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently the PublishResultCoder in SnsIO only serializes the messageId field
> so the PublishResult returned by Beam returns null for
> getSdkResponseMetadata() and getSdkHttpMetadata(). This makes it impossible
> to check the HTTP status for errors, which is necessary since this is not
> handled in SnsIO.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
