pnowojski opened a new pull request #9017: [FLINK-13013][network] Request 
partitions during InputGate#setup
URL: https://github.com/apache/flink/pull/9017
 
 
   Before partitions were being requested on first polling/getting next buffer 
which was causing a couple of issues:
   - it was a little bit confusing
   - after first requestPartitions call, this was causing unnecessary 
synchronisation overhead
   - this was preventing data notifications to come through and isAvailable() 
future was always not completed before the first attempt to read the data from 
the input gate
   
   On top of that, this PR includes a couple of hotfixes, for which please look 
at the individual commits/commit messages.
   
   ## Verifying this change
   
   This change is covered by existing unit and integration tests and it also 
adds a new unit test to add a test coverage for one issue found by ITCase.
   ## 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

Reply via email to