[
https://issues.apache.org/jira/browse/BEAM-5638?focusedWorklogId=199438&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-199438
]
ASF GitHub Bot logged work on BEAM-5638:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Feb/19 21:24
Start Date: 15/Feb/19 21:24
Worklog Time Spent: 10m
Work Description: jklukas commented on issue #7736: [BEAM-5638] Exception
handling for Java MapElements and FlatMapElements
URL: https://github.com/apache/beam/pull/7736#issuecomment-464205343
> * In my use cases, wanting to keep the input element seems to be a
pretty common case -- at the very least to be able to help debug what was bad
about it.
Yes, I agree that is a common case. The `ExceptionAsMapHandler` in this PR
is intended both as an example and as a simple handler that preserves the input
element along with some basic info about the exception that was raised.
> * One thing that I have found myself wishing for frequently is for
exceptions to go into an `Either`, i.e. for the return value of the
`MapElements` to be a: `PCollection<Either<ExceptionT, SuccessT>>` Having a
standard "blessed" way to do this would be very helpful. I've been meaning to
try to contribute something like this but haven't been able to make the time
yet.
I've been assuming that routing successes and failures to separate
collections would be most convenient. I hadn't really considered the
possibility of returning a collection of some `Either`-like class. That seems
more complicated from the perspective of specifying coders, and I expect that
users would often need to follow up with mappers to separate out successes and
failures to different places, but I'd love to hear more details of your use
case.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 199438)
Time Spent: 5.5h (was: 5h 20m)
Remaining Estimate: 162.5h (was: 162h 40m)
> Add exception handling to single message transforms in Java SDK
> ---------------------------------------------------------------
>
> Key: BEAM-5638
> URL: https://issues.apache.org/jira/browse/BEAM-5638
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Jeff Klukas
> Assignee: Jeff Klukas
> Priority: Minor
> Labels: triaged
> Original Estimate: 168h
> Time Spent: 5.5h
> Remaining Estimate: 162.5h
>
> Add methods to MapElements, FlatMapElements, and Filter that allow users to
> specify expected exceptions and tuple tags to associate with the with
> collections of the successfully and unsuccessfully processed elements.
> See discussion on dev list:
> https://lists.apache.org/thread.html/936ed2a5f2c01be066fd903abf70130625e0b8cf4028c11b89b8b23f@%3Cdev.beam.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
