zhijiangW opened a new pull request #9483: [FLINK-13767][task] Migrate isFinished method from AvailabilityListener to AsyncDataInput URL: https://github.com/apache/flink/pull/9483 ## What is the purpose of the change `AvailabilityListener` is used both in `AsyncDataInput` and `StreamTaskInput`. We already introduced `InputStatus` for `PushBasedAsyncDataInput#emitNext`, and then `InputStatus#END_OF_INPUT` has the same semantic with `AvailabilityListener#isFinished`. But for the case of `AsyncDataInput` which is mainly used by `InputGate` layer, the `isFinished()` method is still needed at the moment. So we migrate this method from AvailabilityListener to `AsyncDataInput`, and refactor the `StreamInputProcessor` implementations by using `InputStatus` to judge the finished state. ## Brief change log - *Migrate `isFinished` method from `AvailabilityListener` to `AsyncDataInput`* - *Refactor the `StreamOneInputProcessor` to judge finished state via `InputStatus`* - *Refactor the `StreamTwoInputSelectableProcessor` to judge finished state via `InputStatus`* ## 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
