lindong28 opened a new pull request, #22092:
URL: https://github.com/apache/flink/pull/22092

   ## What is the purpose of the change
   
   Flink 1.15 and later versions require at least Java 11 to build from sources 
[1], whereas the pom.xml specifies the source/target is 1.8. This inconsistency 
confuses users.
   
   As mentioned in the 
[FLINK-25247](https://issues.apache.org/jira/browse/FLINK-25247) title, the 
goal of that ticket is to "Inform users about deprecation". It will be better 
to inform users that "Java 8 is deprecated" instead of saying "Fink requires at 
least Java 11 to build", so that users have the right information to make the 
right choice for themselves.
   
   Also note that Flink community is regularly running flink-ml benchmark for 
both Java 8 and Java 11 [2], which suggests that we are practically ensuring 
Java 8 is supported.
   
   [1] 
https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/flinkdev/building/
   [2] http://codespeed.dak8s.net:8000/timeline/?ben=mapSink.F27_UNBOUNDED&env=2
   
   
   ## Brief change log
   
   Update Flink doc to mention that "Java 8 is deprecated" instead of saying 
"Flink requires at least Java 11 to build".
   
   ## Verifying this change
   
   N/A.
   
   ## 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, 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? N/A
   


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to