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



##########
File path: docs/dev/table/connectors/formats/debezium.zh.md
##########
@@ -167,41 +167,39 @@ Format Options
       <td>required</td>
       <td style="word-wrap: break-word;">(none)</td>
       <td>String</td>
-      <td>Specify what format to use, here should be 
<code>'debezium-json'</code>.</td>
+      <td>指定要使用的格式,此处应为 <code>'debezium-json'</code>。</td>
     </tr>
     <tr>
       <td><h5>debezium-json.schema-include</h5></td>
       <td>optional</td>
       <td style="word-wrap: break-word;">false</td>
       <td>Boolean</td>
-      <td>When setting up a Debezium Kafka Connect, users may enable a Kafka 
configuration <code>'value.converter.schemas.enable'</code> to include schema 
in the message.
-          This option indicates whether the Debezium JSON message includes the 
schema or not. </td>
+      <td>设置 Debezium Kafka Connect 时,用户可以启用 Kafka 配置 
<code>'value.converter.schemas.enable'</code> 以在消息中包含 schema。此选项表明 Debezium 
JSON 消息是否包含 schema。</td>
     </tr>
     <tr>
       <td><h5>debezium-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>
+      <td>跳过带有解析错误的字段和行,而不是失败。如果发生错误,则字段设置为 null。</td>
     </tr>
     <tr>
       <td><h5>debezium-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>:
+      <td>指定输入和输出时间戳格式。当前支持的值为 <code>'SQL'</code> 和 <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>
+        <li>选项 <code>'SQL'</code> 将解析为 "yyyy-MM-dd HH:mm:ss.s{precision}" 
格式的输入时间戳, 例如 '2020-12-30 12:13:14.123' 并输出相同格式的时间戳记。</li>
+        <li>选项 <code>'ISO-8601'</code> 将解析为 "yyyy-MM-ddTHH:mm:ss.s{precision}" 
格式的输入时间戳, 例如 '2020-12-30T12:13:14.123' 并输出相同格式的时间戳记。</li>
       </ul>
       </td>
     </tr>
     </tbody>
 </table>
 
-Data Type Mapping
+数据类型映射
 ----------------
 
-Currently, the Debezium format uses JSON format for deserialization. Please 
refer to [JSON format documentation]({% link 
dev/table/connectors/formats/json.zh.md %}#data-type-mapping) for more details 
about the data type mapping.
+目前,Debezium Format 使用 JSON 格式进行反序列化。有关数据类型映射的更多详细信息,请参考 [JSON format 文档]({% 
link /zh/dev/table/connectors/formats/json.zh.md %}#data-type-mapping)。

Review comment:
       ```suggestion
   目前,Debezium Format 使用 JSON 格式进行反序列化。有关数据类型映射的更多详细信息,请参考 [JSON format 文档]({% 
link dev/table/connectors/formats/json.zh.md %}#data-type-mapping)。
   ```




----------------------------------------------------------------
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:
us...@infra.apache.org


Reply via email to