zhijiangW opened a new pull request #9477: [FLINK-13765][task] Introduce the InputSelectionHandler for selecting next input in StreamTwoInputSelectableProcessor URL: https://github.com/apache/flink/pull/9477 ## What is the purpose of the change 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` and `StreamTwoInputSelectableProcessor` later. ## Brief change log - *Introduce the `InputSelectionHandler` for handling the logic of next available input index* - *Refactor the related process in `StreamTwoInputSelectableProcessor` based on `InputSelectionHandler`* ## 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: [email protected] With regards, Apache Git Services
