zhijiangW opened a new pull request #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478 ## What is the purpose of the change 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. ## Brief change log - *Refactor the constructor of `StreamOneInputProcessor`* - *Refactor the constructor of `StreamTwoInputSelectableProcessor`* - *Introduce `InputStatus` and `StreamTaskInput#emitNext(Output)`* - *Refactor the implementation of `StreamOneInputProcessor`* - *Refactor the implementation of `StreamTwoInputSelectableProcessor`* ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
