[jira] [Resolved] (FLINK-8755) SpilledSubpartitionView wrongly relys on the backlog for determining whether more data is available

["Stephan Ewen (JIRA)" <ji...@apache.org>]

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

Stephan Ewen resolved FLINK-8755.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

Fixed in
  - 1.5.0 via 5c7457aa2aece89b77e9a9402cc514f90e083a69 and d1a969f7ad018ef44f40f974eb49ba004494fcdf
  - 1.6.0 via 18b75e32bb8f4f155f729574b2d377459104471e and c19df9ff670c06aeb381339c244bbd22fe13fd4d

> SpilledSubpartitionView wrongly relys on the backlog for determining whether more data is available
> ---------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-8755
>                 URL: https://issues.apache.org/jira/browse/FLINK-8755
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Network
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Blocker
>             Fix For: 1.5.0, 1.6.0
>
>
> {code}
> public BufferAndBacklog getNextBuffer() throws IOException, InterruptedException {
> //...
>         int newBacklog = parent.decreaseBuffersInBacklog(current);
>         return new BufferAndBacklog(current, newBacklog > 0, newBacklog, nextBufferIsEvent);
> {code}
> relies on the backlog to signal further data availability. However, if there are only events left in the buffer queue, their buffers are not included in the backlog counting and therefore, {{isMoreAvailable}} will be wrongly {{false}} here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)