You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:50:05 UTC

[jira] [Updated] (BEAM-12729) Suppress Avro Runtime Exceptions for Streaming

     [ https://issues.apache.org/jira/browse/BEAM-12729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-12729:
-----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Suppress Avro Runtime Exceptions for Streaming 
> -----------------------------------------------
>
>                 Key: BEAM-12729
>                 URL: https://issues.apache.org/jira/browse/BEAM-12729
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-avro
>            Reporter: Dylan Hercher
>            Priority: P3
>              Labels: streaming
>   Original Estimate: 2h
>          Time Spent: 40m
>  Remaining Estimate: 1h 20m
>
> The current design of ReadFileRangesFn continually throws any un-recoverable errors until the pipeline is turned down for streaming pipelines.
>  
> These invalid file errors do not have a resolvable solution and should be logged as errors for the files in question to allow the pipeline to continue progressing.
>  
> As a file which cannot be read will never recover via a dead letter queue design.  Since no recovery is possible we can simply log the errored file and continue processing.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)