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 02:46:00 UTC

[jira] [Updated] (FLINK-13765) Introduce the TwoInputSelectionHandler for selecting input in StreamTwoInputSelectableProcessor

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

zhijiang updated FLINK-13765:
-----------------------------
    Summary: Introduce the TwoInputSelectionHandler for selecting input in StreamTwoInputSelectableProcessor  (was: Introduce the InputSelectionHandler for selecting next input in StreamTwoInputSelectableProcessor)

> Introduce the 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: 10m
>  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. It would bring two problems:
>  * From design aspect, these fields should be abstracted into a separate component and passed into StreamTwoInputSelectableProcessor.
>  * inputSelector.nextSelection() is called while processing elements in  StreamTwoInputSelectableProcessor, so it is the blocker for integrating task input/output for both StreamOneInputProcessor/StreamTwoInputSelectableProcessor later.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)