You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@avro.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2026/07/13 04:48:00 UTC
[jira] [Assigned] (AVRO-4307) [javascript] BlockDecoder should destroy itself on decompression error to stop upstream I/O
[ https://issues.apache.org/jira/browse/AVRO-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismaël Mejía reassigned AVRO-4307:
----------------------------------
> [javascript] BlockDecoder should destroy itself on decompression error to stop upstream I/O
> -------------------------------------------------------------------------------------------
>
> Key: AVRO-4307
> URL: https://issues.apache.org/jira/browse/AVRO-4307
> Project: Apache Avro
> Issue Type: Improvement
> Components: javascript
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: Major
>
> When a BlockDecoder used via createFileDecoder (ReadStream.pipe(BlockDecoder)) hits a decompression/size error, it emits an error event but does not destroy itself. The upstream file stream can continue reading and feeding data after the error, doing unnecessary I/O/CPU work and possibly emitting multiple errors. BlockDecoder should tear down (destroy) on a fatal error so the pipe unwinds. This touches the hand-rolled finish/push(null) lifecycle in files.js and needs careful testing; split out from AVRO-4287.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)