Skip to content

Conversation

lindong28
Copy link
Member

@lindong28 lindong28 commented Dec 25, 2022

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

If we decide to official drop Java 8 support, Flink community probably should give explicit notice regarding the deprecation period so that users can be prepared for this breaking change. We can follow the Kafka website doc [3] for example, which says "Java 8, Java 11, and Java 17 are supported. Note that Java 8 support has been deprecated since Apache Kafka 3.0 and will be removed in Apache Kafka 4.0".

[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
[3] https://kafka.apache.org/documentation/

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

@lindong28
Copy link
Member Author

@zentol Would you have time to review this PR?

@lindong28
Copy link
Member Author

@flinkbot run azure

@flinkbot
Copy link
Collaborator

flinkbot commented Dec 25, 2022

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@lindong28
Copy link
Member Author

@flinkbot run azure

@lindong28
Copy link
Member Author

lindong28 commented Dec 25, 2022

The CI failed because the container is still using Java 8 to build Flink sources [1]. We need to address FLINK-25250 before merging this PR.

[1] https://github.com/apache/flink/blob/master/azure-pipelines.yml#L42

@MartijnVisser MartijnVisser requested a review from zentol December 27, 2022 09:21
@zentol
Copy link
Contributor

zentol commented Jan 12, 2023

Closing the PR as per my JIRA comment.

@zentol zentol closed this Jan 12, 2023
@lindong28 lindong28 reopened this Jan 12, 2023
@lindong28
Copy link
Member Author

@zentol I have re-opened the PR per my JIRA comment. Maybe we can continue the technical discussion there.

@lindong28 lindong28 removed the request for review from zentol January 18, 2023 03:30
@lindong28 lindong28 changed the title [FLINK-30501] Set requireJavaVersion in pom.xml to be at least 11 [FLINK-30501] Update Flink build instruction to deprecate Java 8 instead of requiring Java 11 Mar 1, 2023
@lindong28
Copy link
Member Author

@zentol @yunfengzhou-hub Do you have time to review this PR?

@lindong28
Copy link
Member Author

@reswqa Can you help review this PR? Thanks!

Copy link
Member

@reswqa reswqa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @lindong28, LGTM!

@lindong28 lindong28 merged commit 88d28a1 into apache:master Mar 6, 2023
@lindong28 lindong28 deleted the FLINK-30501 branch April 3, 2023 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants