WencongLiu commented on code in PR #23362: URL: https://github.com/apache/flink/pull/23362#discussion_r1369706754
########## docs/content/docs/dev/datastream/how_to_migrate_from_dataset_to_datastream.md: ########## @@ -0,0 +1,660 @@ +--- +title: "How To Migrate From DataSet to DataStream" +weight: 302 +type: docs +bookToc: false +aliases: + - /dev/how_to_migrate_from_dataset_to_datastream.html +--- +<!-- +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. +--> + +# How To Migrate From DataSet to DataStream + +The DataSet API has been formally deprecated and will no longer receive active maintenance and support. It will be removed in the +Flink 2.0 version. Flink users are recommended to migrate from the DataSet API to the DataStream API, Table API and SQL for their +data processing requirements. DataSet operators can be implemented by the DataStream API. However, it's important to note that Review Comment: 1. A new paragraph is started here. 2. Good point. I have reorganized the entire paragraph. ########## docs/content/docs/dev/datastream/how_to_migrate_from_dataset_to_datastream.md: ########## @@ -0,0 +1,660 @@ +--- +title: "How To Migrate From DataSet to DataStream" +weight: 302 +type: docs +bookToc: false +aliases: + - /dev/how_to_migrate_from_dataset_to_datastream.html +--- +<!-- +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. +--> + +# How To Migrate From DataSet to DataStream + +The DataSet API has been formally deprecated and will no longer receive active maintenance and support. It will be removed in the +Flink 2.0 version. Flink users are recommended to migrate from the DataSet API to the DataStream API, Table API and SQL for their +data processing requirements. DataSet operators can be implemented by the DataStream API. However, it's important to note that +different operators have varying costs in the implementation, and they can be categorized into three types: + +1. The first type of operators are quite similar to DataStream in terms of API usage. They can be easily implemented without much +complexity. +2. The second type of operators, on the other hand, have completely different names and API usage in DataStream. This can make the +job code more complex. +3. Lastly, the third type of operators not only have different names and API usage in DataStream, but they also involve additional +computation and shuffle costs. Review Comment: I have divided all DataSet APIs into four categories, with the fourth category being unsupported. -- 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]
