kl0u opened a new pull request #12317:
URL: https://github.com/apache/flink/pull/12317


   ## What is the purpose of the change
   
   This PR simply changes the error message presented to the user when he/she 
is trying to submit to Yarn but hadoop is not in the classpath. The new message 
will be:
   
   ```
   No Executor found. Please make sure to have hadoop in your classpath. For 
more information on how to do so refer to the "Deployment & Operations" section 
of the official Apache Flink documentation.
   ```
   
   ## Brief change log
   
   The changes are:
    1. a `FallbackYarnSessionCli` that will be loaded by the `CliFrontend` in 
case there is a loading error when the frontend tries to load the actual 
`FlinkYarnSessionCli`. This cli will simply throw an exception with the above 
message when it detects that the `FlinkYarnSessionCli` would be used but it 
failed to be loaded (the `isActive` method).
    2. change of the error message in the `YarnJobClusterExecutorFactory` and 
the `YarnSessionClusterExecutorFactory` when the executor cannot be 
instantiated. This is to cover for the case where the user tries to access a 
Yarn cluster through the `ExecutorCLI`.
   
   ## Verifying this change
   
   Was verified manually and also added the `FallbackYarnSessionCliTest`.
   
   ## 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, Kubernetes/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]


Reply via email to