zentol commented on code in PR #19584: URL: https://github.com/apache/flink/pull/19584#discussion_r859688107
########## docs/content/release-notes/flink-1.15.md: ########## @@ -0,0 +1,614 @@ +--- +title: "Release Notes - Flink 1.15" +--- +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +# Release notes - Flink 1.15 + +These release notes discuss important aspects, such as configuration, behavior, +or dependencies, that changed between Flink 1.14 and Flink 1.15. Please read these +notes carefully if you are planning to upgrade your Flink version to 1.15. + +## Summary of changed dependency names + +There are Several changes in Flink 1.15 that require updating dependency names when +upgrading from earlier versions, mainly including the effort to opting-out Scala dependencies +from non-scala modules and reorganize table modules. A quick checklist of the dependency changes +is as follows: + +* Any dependency to one of the following modules needs to be updated to no longer include a suffix: + + ``` + flink-cep + flink-clients + flink-connector-elasticsearch-base + flink-connector-elasticsearch5 + flink-connector-elasticsearch6 + flink-connector-elasticsearch7 + flink-connector-gcp-pubsub + flink-connector-hbase-1.4 + flink-connector-hbase-2.2 + flink-connector-hbase-base + flink-connector-jdbc + flink-connector-kafka + flink-connector-kinesis + flink-connector-nifi + flink-connector-pulsar + flink-connector-rabbitmq + flink-connector-testing + flink-connector-twitter + flink-connector-wikiedits + flink-container + flink-dstl-dfs + flink-gelly + flink-hadoop-bulk + flink-kubernetes + flink-runtime-web + flink-sql-connector-elasticsearch6 + flink-sql-connector-elasticsearch7 + flink-sql-connector-hbase-1.4 + flink-sql-connector-hbase-2.2 + flink-sql-connector-kafka + flink-sql-connector-kinesis + flink-sql-connector-rabbitmq + flink-state-processor-api + flink-statebackend-rocksdb + flink-streaming-java + flink-table-api-java-bridge + flink-test-utils + flink-yarn + flink-table-uber + flink-table-runtime + flink-orc + flink-orc-nohive + flink-parquet + ``` +* For Table / SQL users, the new module `flink-table-planner-loader` replaces `flink-table-planner_2.12` + and avoids the need for a Scala suffix. As a consequence, `flink-table-uber` has been split into `flink-table-api-java-uber`, + `flink-table-planner(-loader)`, and `flink-table-runtime`. `flink-sql-client` has no Scala suffix anymore. + Scala users need to explicitly add a dependency to `flink-table-api-scala` or `flink-table-api-scala-bridge`. + For backwards compatibility, users can still swap it with `flink-table-planner_2.12` located in `opt/`. + +The detail of the involved issues are listed as follows. + +#### Add support for opting-out of Scala + +##### [FLINK-20845](https://issues.apache.org/jira/browse/FLINK-20845) + +The Java DataSet/-Stream APIs are now independent of Scala and no longer transitively depend on it. + +The implications are the following: + +* If you only intend to use the Java APIs, with Java types, +then you can opt-in to a Scala-free Flink by removing the `flink-scala` jar from the `lib/` directory of the distribution. +You are then free to use any Scala version and Scala libraries. +You can either bundle Scala itself in your user-jar; or put into the `lib/` directory of the distribution. + +* If you relied on the Scala APIs, without an explicit dependency on them, + then you may experience issues when building your projects. You can solve this by adding explicit dependencies to + the APIs that you are using. This should primarily affect users of the Scala `DataStream/CEP` APIs. + +* A lot of modules have lost their Scala suffix. + Any dependency on one of the modules listed below needs to be updated. Review Comment: ```suggestion ``` -- 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]
