You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/06/13 12:52:28 UTC

[GitHub] [flink] sunhaibotb opened a new pull request #8731: [FLINK-11878][runtime] Implement the runtime handling of BoundedOneInput and BoundedMultiInput

sunhaibotb opened a new pull request #8731: [FLINK-11878][runtime] Implement the runtime handling of BoundedOneInput and BoundedMultiInput
URL: https://github.com/apache/flink/pull/8731
 
 
   ## What is the purpose of the change
   
   This pull request implements the runtime handling of the BoundedOneInput and BoundedMultiInput 
    interfaces. This will give the bounded stream operators an opportunity to process certain logic when the EndOfInput  notification arrives.  For example,  the hash join operator knows when the read to the build side has finished, then it can finish the build phase and prepare for the probe phase.
   
   
   ## Brief change log
   
     - Change `xInputProcessor` (`StreamInputProcessor`, `StreamTwoInputProcessor` and `StreamTwoInputSelecdtableProcessor`) to add the `endInput()` method call of the header operator on the operator chain.
     - Change `xStreamTask` (`SourceStreamTask`, `OneInputStreamTask`, `TwoInputStreamTask` and `TwoInputSelectableStreamTask`) to add the `endInput()` method calls for other non-header operators on the operator chain.
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - Added test that validates that `SourceStreamTask` correctly handles `EndOfInput` notifications.
     - Added test that validates that `OneInputStreamTask` correctly handles `EndOfInput` notifications.
     - Added test that validates that `TwoInputStreamTask` correctly handles `EndOfInput` notifications.
     - Added test that validates that `TwoInputSelectableStreamTask` correctly handles `EndOfInput` notifications.
   
   ## 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:
users@infra.apache.org


With regards,
Apache Git Services