You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "zhijiang (Jira)" <ji...@apache.org> on 2019/08/27 08:08:00 UTC
[jira] [Closed] (FLINK-13765) Introduce TwoInputSelectionHandler
for selecting input in StreamTwoInputSelectableProcessor
[ https://issues.apache.org/jira/browse/FLINK-13765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhijiang closed FLINK-13765.
----------------------------
Resolution: Fixed
Fixed in master : 261c2dc8ed247a5b49594b87b1e8c2dc84dd5206
> Introduce TwoInputSelectionHandler for selecting input in StreamTwoInputSelectableProcessor
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-13765
> URL: https://issues.apache.org/jira/browse/FLINK-13765
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Task
> Reporter: zhijiang
> Assignee: zhijiang
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In StreamTwoInputSelectableProcessor there are three fields \{InputSelectable, InputSelection, availableInputsMask} to be used together for the function of selecting next available input index.
> From design aspect, these fields can be abstracted into a separate component called TwoInputSelectionHandler, which is passed into the constructor of StreamTwoInputSelectableProcessor as a final field. So the internal implementation details of TwoInputSelectionHandler is hidden from processor view which only needs to interact with exposed methods from selection handler.
> Another tiny benefit is that we make the StreamTwoInputSelectableProcessor a bit because two methods are removed from it.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)