[
https://issues.apache.org/jira/browse/BEAM-5638?focusedWorklogId=201603&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-201603
]
ASF GitHub Bot logged work on BEAM-5638:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Feb/19 20:51
Start Date: 20/Feb/19 20:51
Worklog Time Spent: 10m
Work Description: tims commented on issue #7736: [BEAM-5638] Exception
handling for Java MapElements and FlatMapElements
URL: https://github.com/apache/beam/pull/7736#issuecomment-465748762
> That would be quite nice, but it does add complexity and restrictions. In
many, cases the type returned in each step of a series of transforms will be
different, and I'd generally expect it will be necessary to define an exception
handler per input type. I'm imagining that often users will want to preserve
the input element along with info about the exception, so that they can
reprocess the failed elements some time in the future.
It's also common to just want all failures to be logged to the same place
per job. And many times, in the steps I want to union the failures for, they
all have a common element type anyway.
You would still be able to stop the chaining at any point if you wanted to
use different error types, by just getting the output() from Result.
Extending the Result class with an apply method to chain ordinary transforms
with exception handling could be nice future PR work, I'm happy to give it a
try. To chain non failure handling transforms with a common exception/failure
handler way, I think would require MapElements and FlatMapElements to have a
common interface or annotation though. So that a Result.apply method could call
`exceptionsVia`/etc on them.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 201603)
Time Spent: 8h 40m (was: 8.5h)
Remaining Estimate: 159h 20m (was: 159.5h)
> 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: 8h 40m
> Remaining Estimate: 159h 20m
>
> 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)
