You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/08/28 15:14:00 UTC

[jira] [Resolved] (FLINK-19087) ReaultPartitionWriter should not expose subpartition but only subpartition-readers

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

Stephan Ewen resolved FLINK-19087.
----------------------------------
    Resolution: Fixed

Fixed in 1.12 via 95c533c964e5babfee5d901ffea3c9be48e30ccb

> ReaultPartitionWriter should not expose subpartition but only subpartition-readers
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-19087
>                 URL: https://issues.apache.org/jira/browse/FLINK-19087
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Network
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Major
>             Fix For: 1.12.0
>
>
> The {{ResultPartitionWiter}} currently gives arbitrary access to the sub-partitions.
> These subpartitions may not always exist directly, such as in a sort based shuffle.
> Necessary is only the access to a reader over a sub-partition's data (the ResultSubpartitionView).
> In the spirit of minimal scope of knowledge, the methods should be scoped to return readers, not the more general subpartitions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)