TisonKun opened a new pull request #11311: [FLINK-16427][api] Remove directly 
throw ProgramInvocationExceptions in RemoteStreamEnvironment
URL: https://github.com/apache/flink/pull/11311
 
 
   ## What is the purpose of the change
   
   This issue is a child issue of FLINK-15090.
   
   With a previous discussion with @aljoscha  we tend to reverse the dependency 
from flink-streaming-java to flink-client so that we have a semantic correct 
module dependency. That says, flink-streaming-java, just like flink-java(batch 
api), is an api module which should not know about the runtime.
   
   This issue closes #11261 .
   
   ## Brief change log
   
   - Remove directly throw `ProgramInvocationExceptions` in 
`RemoteStreamEnvironment`
   
   ## 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): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes, we possibly change the actual exception thrown from 
`RemoteStreamEnvironment#execute`, it is previously always 
`ProgramInvocationException` which is an unfortunately accident. We change the 
behavior for reverse the dependency from flink-streaming-java to flink-client 
in the future)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   
   cc @tillrohrmann 
   

----------------------------------------------------------------
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