XComp opened a new pull request #15673:
URL: https://github.com/apache/flink/pull/15673


   ## What is the purpose of the change
   
   According to the discussion on the dev mailing list ([[SURVEY] Remove Mesos 
support](http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/SURVEY-Remove-Mesos-support-td45974.html)
 and [[VOTE] Deprecating Mesos 
support](http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Deprecating-Mesos-support-td50142.html)),
 the community decided to deprecate Mesos support in Apache Flink (see 
[[RESULT][VOTE]Deprecating Mesos 
support](http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/RESULT-VOTE-Deprecating-Mesos-support-td50260.html)).
   
   
   ## Brief change log
   
   * Adds `@Deprecated` note to Mesos-related implementations and extended the 
corresponding JavaDoc
   * Adds a warning to the intro of the Flink on Mesos documentation and 
Flink's Mesos-specific configuration subsection in the docs
   * Adds log statement to `MesosJobClusterEntrypoint` and 
`MesosSessionClusterEntrypoint`
   
   ## Verifying this change
   
   Build docs locally and verified that the warning is shown.
   
   ## 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)`: no
     - 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? yes
     - If yes, how is the feature documented? docs & JavaDocs
   


-- 
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:
us...@infra.apache.org


Reply via email to