You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2019/09/23 10:44:00 UTC

[jira] [Closed] (FLINK-13766) Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext

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

Piotr Nowojski closed FLINK-13766.
----------------------------------
    Fix Version/s: 1.10.0
       Resolution: Fixed

Merged as a80bbf187b8a7318db3a8b117e7281eaa174c647

> Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-13766
>                 URL: https://issues.apache.org/jira/browse/FLINK-13766
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Task
>            Reporter: zhijiang
>            Assignee: zhijiang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current processing in task input processor is based on the way of pollNext. In order to unify the processing way of new source operator, we introduce the new StreamTaskInput#emitNext(Output) instead of current pollNext. Then we need to adjust the existing implementations of StreamOneInputProcessor/StreamTwoInputSelectableProcessor based on the new emit way.
> To do so, we could integrate all the task inputs from network/source in a unified processing on runtime side.



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