You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/10/10 17:25:01 UTC
[jira] [Commented] (BEAM-12729) Suppress Avro Runtime Exceptions
for Streaming
[ https://issues.apache.org/jira/browse/BEAM-12729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426832#comment-17426832 ]
Beam JIRA Bot commented on BEAM-12729:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2, 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.3.4#803005)