We could pass a `Contextful` here, in which case we'd be able to let the `IOException` bubble up rather than catching and rethrowing as unchecked (which we do for the new `WithFailures` code below). But that could potentially break existing user code if users catch `PipelineExecutionException` and check the cause. That seems unlikely, so perhaps switching to a `Contextful` to avoid rethrowing is an option.
In lieu of that, I've changed this to the more specific `UncheckedIOException`, which inherits from `RuntimeException` so is a safer change. This all applies to `ParseJsons` too. [ Full content available at: https://github.com/apache/beam/pull/6586 ] This message was relayed via gitbox.apache.org for [email protected]
