You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/07/04 08:25:00 UTC
[jira] [Updated] (FLINK-13097) Buffer depletion in
SimpleCollectingOutputView throws non-obvious EOFException
[ https://issues.apache.org/jira/browse/FLINK-13097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-13097:
-----------------------------------
Labels: pull-request-available (was: )
> Buffer depletion in SimpleCollectingOutputView throws non-obvious EOFException
> -------------------------------------------------------------------------------
>
> Key: FLINK-13097
> URL: https://issues.apache.org/jira/browse/FLINK-13097
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 1.7.2, 1.8.0
> Environment: SCIO + BEAM + Flink under scala 2.12, java 8
> Reporter: Cyrille Chépélov
> Priority: Trivial
> Labels: pull-request-available
>
> When SimpleCollectingOutputView is used, records are collected into a pre-allocated MemorySegmentSource.
> In case of depletion, the SimpleCollectingOutputView#nextSegment method throws EOFException without a message.
> This can be non-obvious to diagnose as a newcomer, as
> * the Java SDK documentation strongly suggests EOFException is related to an inability to read further (whereas in this context, the exception materializes an inability to _write_ further)
> * awareness than pre-allocated, fixed-size buffers are in play may not necessarily be expected of a newcomer to flink.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)