wuchong commented on a change in pull request #14245:
URL: https://github.com/apache/flink/pull/14245#discussion_r537226135



##########
File path: docs/dev/table/connectors/formats/maxwell.md
##########
@@ -0,0 +1,212 @@
+---
+title: "Maxwell Format"
+nav-title: Maxwell
+nav-parent_id: sql-formats
+nav-pos: 6
+---
+<!--
+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.
+-->
+
+<span class="label label-info">Changelog-Data-Capture Format</span>
+<span class="label label-info">Format: Serialization Schema</span>
+<span class="label label-info">Format: Deserialization Schema</span>
+
+* This will be replaced by the TOC
+{:toc}
+
+[Maxwell](https://maxwells-daemon.io/) is a CDC (Changelog Data Capture) tool 
that can stream changes in real-time from MySQL into Kafka, Kinesis and other 
streaming connectors. Maxwell provides a unified format schema for changelog 
and supports to serialize messages using JSON.
+
+Flink supports to interpret Maxwell JSON messages as INSERT/UPDATE/DELETE 
messages into Flink SQL system. This is useful in many cases to leverage this 
feature, such as
+ - synchronizing incremental data from databases to other systems
+ - auditing logs
+ - real-time materialized views on databases
+ - temporal join changing history of a database table and so on.
+
+Flink also supports to encode the INSERT/UPDATE/DELETE messages in Flink SQL 
as Maxwell JSON messages, and emit to external systems like Kafka.
+However, currently Flink can't combine UPDATE_BEFORE and UPDATE_AFTER into a 
single UPDATE message. Therefore, Flink encodes UPDATE_BEFORE and UDPATE_AFTER 
as DELETE and INSERT Maxwell messages.
+
+Dependencies
+------------
+
+<div class="codetabs" markdown="1">
+<div data-lang="Maxwell" markdown="1">

Review comment:
       We don't need the Maxwell tab. 

##########
File path: docs/dev/table/connectors/formats/index.md
##########
@@ -73,6 +73,11 @@ Flink supports the following formats:
           <td><a href="{% link dev/table/connectors/kafka.md %}">Apache 
Kafka</a>,
            <a href="{% link dev/table/connectors/filesystem.md 
%}">Filesystem</a></td>
         </tr>
+        <tr>
+         <td><a href="{% link dev/table/connectors/formats/canal.md 
%}">Maxwell CDC</a></td>

Review comment:
       ```suggestion
            <td><a href="{% link dev/table/connectors/formats/maxwell.md 
%}">Maxwell CDC</a></td>
   ```

##########
File path: docs/dev/table/connectors/formats/maxwell.md
##########
@@ -0,0 +1,212 @@
+---
+title: "Maxwell Format"
+nav-title: Maxwell
+nav-parent_id: sql-formats
+nav-pos: 6
+---
+<!--
+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.
+-->
+
+<span class="label label-info">Changelog-Data-Capture Format</span>
+<span class="label label-info">Format: Serialization Schema</span>
+<span class="label label-info">Format: Deserialization Schema</span>
+
+* This will be replaced by the TOC
+{:toc}
+
+[Maxwell](https://maxwells-daemon.io/) is a CDC (Changelog Data Capture) tool 
that can stream changes in real-time from MySQL into Kafka, Kinesis and other 
streaming connectors. Maxwell provides a unified format schema for changelog 
and supports to serialize messages using JSON.
+
+Flink supports to interpret Maxwell JSON messages as INSERT/UPDATE/DELETE 
messages into Flink SQL system. This is useful in many cases to leverage this 
feature, such as
+ - synchronizing incremental data from databases to other systems
+ - auditing logs
+ - real-time materialized views on databases
+ - temporal join changing history of a database table and so on.
+
+Flink also supports to encode the INSERT/UPDATE/DELETE messages in Flink SQL 
as Maxwell JSON messages, and emit to external systems like Kafka.
+However, currently Flink can't combine UPDATE_BEFORE and UPDATE_AFTER into a 
single UPDATE message. Therefore, Flink encodes UPDATE_BEFORE and UDPATE_AFTER 
as DELETE and INSERT Maxwell messages.
+
+Dependencies
+------------
+
+<div class="codetabs" markdown="1">
+<div data-lang="Maxwell" markdown="1">
+{% assign connector = site.data.sql-connectors['maxwell'] %}
+{% include sql-connector-download-table.html
+    connector=connector
+%}
+</div>
+</div>
+
+*Note: please refer to [Maxwell 
documentation](http://maxwells-daemon.io/quickstart/) about how to synchronize 
changelog to Kafka topics with Maxwell JSON.*
+
+
+How to use Maxwell format
+----------------
+
+Maxwell provides a unified format for changelog, here is a simple example for 
an update operation captured from a MySQL `products` table in JSON format:
+
+```json
+{
+   "database":"test",
+   "table":"e",
+   "type":"insert",
+   "ts":1477053217,
+   "xid":23396,
+   "commit":true,
+   "position":"master.000006:800911",
+   "server_id":23042,
+   "thread_id":108,
+   "primary_key": [1, "2016-10-21 05:33:37.523000"],
+   "primary_key_columns": ["id", "c"],
+   "data":{
+     "id":111,
+     "name":"scooter",
+     "description":"Big 2-wheel scooter",
+     "weight":5.15
+   },
+   "old":{
+     "weight":5.18,
+   }
+}
+```
+
+*Note: please refer to [Maxwell 
documentation](http://maxwells-daemon.io/dataformat/) about the meaning of each 
fields.*
+
+The MySQL `products` table has 4 columns (`id`, `name`, `description` and 
`weight`). The above JSON message is an update change event on the `products` 
table where the `weight` value of the row with `id = 111` is changed from 
`5.18` to `5.15`.
+Assuming this messages is synchronized to Kafka topic `products_binlog`, then 
we can use the following DDL to consume this topic and interpret the change 
events.
+
+<div class="codetabs" markdown="1">
+<div data-lang="SQL" markdown="1">
+{% highlight sql %}
+CREATE TABLE topic_products (
+  -- schema is totally the same to the MySQL "products" table
+  id BIGINT,
+  name STRING,
+  description STRING,
+  weight DECIMAL(10, 2)
+) WITH (
+ 'connector' = 'kafka',
+ 'topic' = 'products_binlog',
+ 'properties.bootstrap.servers' = 'localhost:9092',
+ 'properties.group.id' = 'testGroup',
+ 'format' = 'maxwell-json'
+)
+{% endhighlight %}
+</div>
+</div>
+
+After registering the topic as a Flink table, then you can consume the Maxwell 
messages as a changelog source.
+
+<div class="codetabs" markdown="1">
+<div data-lang="SQL" markdown="1">
+{% highlight sql %}
+-- a real-time materialized view on the MySQL "products"
+-- which calculate the latest average of weight for the same products
+SELECT name, AVG(weight) FROM topic_products GROUP BY name;
+
+-- synchronize all the data and incremental changes of MySQL "products" table 
to
+-- Elasticsearch "products" index for future searching
+INSERT INTO elasticsearch_products
+SELECT * FROM topic_products;
+{% endhighlight %}
+</div>
+</div>
+
+Format Options
+----------------
+
+<div data-lang="Maxwell Json" markdown="1">
+
+<table class="table table-bordered">
+    <thead>
+      <tr>
+        <th class="text-left" style="width: 25%">Option</th>
+        <th class="text-center" style="width: 8%">Required</th>
+        <th class="text-center" style="width: 7%">Default</th>
+        <th class="text-center" style="width: 10%">Type</th>
+        <th class="text-center" style="width: 50%">Description</th>
+      </tr>
+    </thead>
+    <tbody>
+    <tr>
+      <td><h5>format</h5></td>
+      <td>required</td>
+      <td style="word-wrap: break-word;">(none)</td>
+      <td>String</td>
+      <td>Specify what format to use, here should be 
<code>'maxwell-json'</code>.</td>
+    </tr>
+    <tr>
+      <td><h5>maxwell-json.ignore-parse-errors</h5></td>
+      <td>optional</td>
+      <td style="word-wrap: break-word;">false</td>
+      <td>Boolean</td>
+      <td>Skip fields and rows with parse errors instead of failing.
+      Fields are set to null in case of errors.</td>
+    </tr>
+    <tr>
+       <td><h5>maxwell-json.timestamp-format.standard</h5></td>
+       <td>optional</td>
+       <td style="word-wrap: break-word;"><code>'SQL'</code></td>
+       <td>String</td>
+       <td>Specify the input and output timestamp format. Currently supported 
values are <code>'SQL'</code> and <code>'ISO-8601'</code>:
+       <ul>
+         <li>Option <code>'SQL'</code> will parse input timestamp in 
"yyyy-MM-dd HH:mm:ss.s{precision}" format, e.g '2020-12-30 12:13:14.123' and 
output timestamp in the same format.</li>
+         <li>Option <code>'ISO-8601'</code>will parse input timestamp in 
"yyyy-MM-ddTHH:mm:ss.s{precision}" format, e.g '2020-12-30T12:13:14.123' and 
output timestamp in the same format.</li>
+       </ul>
+       </td>
+    </tr>
+    <tr>
+      <td><h5>maxwell-json.map-null-key.mode</h5></td>
+      <td>optional</td>
+      <td style="word-wrap: break-word;"><code>'FAIL'</code></td>
+      <td>String</td>
+      <td>Specify the handling mode when serializing null keys for map data. 
Currently supported values are <code>'FAIL'</code>, <code>'DROP'</code> and 
<code>'LITERAL'</code>:
+      <ul>
+        <li>Option <code>'FAIL'</code> will throw exception when encountering 
map with null key.</li>
+        <li>Option <code>'DROP'</code> will drop null key entries for map 
data.</li>
+        <li>Option <code>'LITERAL'</code> will replace null key with string 
literal. The string literal is defined by 
<code>debezium-json.map-null-key.literal</code> option.</li>

Review comment:
       Please fix all the "debezium".

##########
File path: docs/dev/table/connectors/formats/index.zh.md
##########
@@ -73,6 +73,11 @@ Flink 支持以下格式:
           <td><a href="{% link dev/table/connectors/kafka.zh.md %}">Apache 
Kafka</a>,
            <a href="{% link dev/table/connectors/filesystem.zh.md 
%}">Filesystem</a></td>
         </tr>
+        <tr>
+         <td><a href="{% link dev/table/connectors/formats/canal.zh.md 
%}">Maxwell CDC</a></td>

Review comment:
       ```suggestion
            <td><a href="{% link dev/table/connectors/formats/maxwell.zh.md 
%}">Maxwell CDC</a></td>
   ```




----------------------------------------------------------------
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:
[email protected]


Reply via email to