KurtYoung commented on a change in pull request #9438: [WIP] [FLINK-13712] 
[docs] Add release notes for Flink 1.9.0
URL: https://github.com/apache/flink/pull/9438#discussion_r314252925

 File path: docs/release-notes/flink-1.9.md
 @@ -0,0 +1,175 @@
+title: "Release Notes - Flink 1.9"
+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
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+These release notes discuss important aspects, such as configuration, behavior,
+or dependencies, that changed between Flink 1.8 and Flink 1.9. It also 
provides an overview
+on known shortcoming or limitations with new experimental features introduced 
in 1.9.
+Please read these notes carefully if you are planning to upgrade your Flink 
version to 1.9.
+* This will be replaced by the TOC
+## Known shortcomings or limitations for new features
+### New Table / SQL Blink runner
 Review comment:
   In Flink 1.9.0, we also added a preview feature about SQL DDL, but only for 
batch style DDLs. So all the streaming related concepts are not supported yet, 
like watermark.
   Related issues:
   - [FLINK-13661: Add a stream specific  CREATE TABLE SQL DDL]
   - [FLINK-13568: DDL create table doesn't allow STRING data type]

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:

With regards,
Apache Git Services

Reply via email to