leonardBang commented on a change in pull request #15235:
URL: https://github.com/apache/flink/pull/15235#discussion_r598385738
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -59,212 +59,208 @@ CREATE TABLE myUserTable (
);
```
-Connector Options
+连接器选项
Review comment:
```suggestion
连接器参数
```
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -24,26 +24,26 @@ specific language governing permissions and limitations
under the License.
-->
-# Elasticsearch SQL Connector
+# Elasticsearch SQL 连接器
{{< label "Sink: Batch" >}}
{{< label "Sink: Streaming Append & Upsert Mode" >}}
-The Elasticsearch connector allows for writing into an index of the
Elasticsearch engine. This document describes how to setup the Elasticsearch
Connector to run SQL queries against Elasticsearch.
+Elasticsearch 连接器允许将数据写入到 Elasticsearch 引擎的索引中。本文档描述如何设置 Elasticsearch 连接器来对
Elasticsearch 运行 SQL 查询。
Review comment:
```suggestion
Elasticsearch 连接器允许将数据写入到 Elasticsearch 引擎的索引中。本文档描述运行 SQL 查询时如何设置
Elasticsearch 连接器。
```
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -24,26 +24,26 @@ specific language governing permissions and limitations
under the License.
-->
-# Elasticsearch SQL Connector
+# Elasticsearch SQL 连接器
{{< label "Sink: Batch" >}}
{{< label "Sink: Streaming Append & Upsert Mode" >}}
-The Elasticsearch connector allows for writing into an index of the
Elasticsearch engine. This document describes how to setup the Elasticsearch
Connector to run SQL queries against Elasticsearch.
+Elasticsearch 连接器允许将数据写入到 Elasticsearch 引擎的索引中。本文档描述如何设置 Elasticsearch 连接器来对
Elasticsearch 运行 SQL 查询。
-The connector can operate in upsert mode for exchanging UPDATE/DELETE messages
with the external system using the primary key defined on the DDL.
+连接器可以在 upsert 模式下操作，使用 DDL 中定义的主键与外部系统交换 UPDATE/DELETE 消息。
Review comment:
```suggestion
连接器可以工作在 upsert 模式，使用 DDL 中定义的主键与外部系统交换 UPDATE/DELETE 消息。
```
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -24,26 +24,26 @@ specific language governing permissions and limitations
under the License.
-->
-# Elasticsearch SQL Connector
+# Elasticsearch SQL 连接器
{{< label "Sink: Batch" >}}
{{< label "Sink: Streaming Append & Upsert Mode" >}}
-The Elasticsearch connector allows for writing into an index of the
Elasticsearch engine. This document describes how to setup the Elasticsearch
Connector to run SQL queries against Elasticsearch.
+Elasticsearch 连接器允许将数据写入到 Elasticsearch 引擎的索引中。本文档描述如何设置 Elasticsearch 连接器来对
Elasticsearch 运行 SQL 查询。
-The connector can operate in upsert mode for exchanging UPDATE/DELETE messages
with the external system using the primary key defined on the DDL.
+连接器可以在 upsert 模式下操作，使用 DDL 中定义的主键与外部系统交换 UPDATE/DELETE 消息。
-If no primary key is defined on the DDL, the connector can only operate in
append mode for exchanging INSERT only messages with external system.
+如果 DDL 中没有定义主键，那么连接器只能在 append 模式下操作，只能与外部系统交换 INSERT 消息。
Review comment:
```suggestion
如果 DDL 中没有定义主键，那么连接器只能工作在 append 模式，只能与外部系统交换 INSERT 消息。
```
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -59,212 +59,208 @@ CREATE TABLE myUserTable (
);
```
-Connector Options
+连接器选项
----------------
<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>
+ <th class="text-left" style="width: 25%">选项</th>
+ <th class="text-center" style="width: 8%">是否必选</th>
+ <th class="text-center" style="width: 7%">默认值</th>
+ <th class="text-center" style="width: 10%">类型</th>
Review comment:
`数据类型` just keep same with other connector pages.
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -59,212 +59,208 @@ CREATE TABLE myUserTable (
);
```
-Connector Options
+连接器选项
----------------
<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>
+ <th class="text-left" style="width: 25%">选项</th>
+ <th class="text-center" style="width: 8%">是否必选</th>
+ <th class="text-center" style="width: 7%">默认值</th>
Review comment:
Good translation, I found existed zh docs use `默认参数` which is not
properly, could you help update them(upsert-kafka.md, datagen.md, hbase.md,
print.md)?
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -59,212 +59,208 @@ CREATE TABLE myUserTable (
);
```
-Connector Options
+连接器选项
----------------
<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>
+ <th class="text-left" style="width: 25%">选项</th>
Review comment:
参数
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -59,212 +59,208 @@ CREATE TABLE myUserTable (
);
```
-Connector Options
+连接器选项
----------------
<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>
+ <th class="text-left" style="width: 25%">选项</th>
+ <th class="text-center" style="width: 8%">是否必选</th>
+ <th class="text-center" style="width: 7%">默认值</th>
+ <th class="text-center" style="width: 10%">类型</th>
+ <th class="text-center" style="width: 50%">描述</th>
</tr>
</thead>
<tbody>
<tr>
<td><h5>connector</h5></td>
- <td>required</td>
+ <td>必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Specify what connector to use, valid values are:
+ <td>指定要使用的连接器，有效值为：
<ul>
- <li><code>elasticsearch-6</code>: connect to Elasticsearch 6.x
cluster</li>
- <li><code>elasticsearch-7</code>: connect to Elasticsearch 7.x and later
versions cluster</li>
+ <li><code>elasticsearch-6</code>：连接到 Elasticsearch 6.x 的集群。</li>
+ <li><code>elasticsearch-7</code>：连接到 Elasticsearch 7.x 及更高版本的集群。</li>
</ul></td>
</tr>
<tr>
<td><h5>hosts</h5></td>
- <td>required</td>
+ <td>必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>One or more Elasticsearch hosts to connect to, e.g.
<code>'http://host_name:9092;http://host_name:9093'</code>.</td>
+ <td>要连接到的一台或多台 Elasticsearch 主机，例如
<code>'http://host_name:9092;http://host_name:9093'</code>。</td>
</tr>
<tr>
<td><h5>index</h5></td>
- <td>required</td>
+ <td>必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Elasticsearch index for every record. Can be a static index (e.g.
<code>'myIndex'</code>) or
- a dynamic index (e.g. <code>'index-{log_ts|yyyy-MM-dd}'</code>).
- See the following <a href="#dynamic-index">Dynamic Index</a> section
for more details.</td>
+ <td>Elasticsearch 中每条记录的索引。可以是一个静态索引（例如
<code>'myIndex'</code>）或一个动态索引（例如 <code>'index-{log_ts|yyyy-MM-dd}'</code>）。
+ 更多详细信息，请参见下面的<a href="#动态索引">动态索引</a>部分。</td>
</tr>
<tr>
<td><h5>document-type</h5></td>
- <td>required in 6.x</td>
+ <td>6.x 版本中必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Elasticsearch document type. Not necessary anymore in
<code>elasticsearch-7</code>.</td>
+ <td>Elasticsearch 文档类型。在 <code>elasticsearch-7</code> 中不再需要。</td>
</tr>
<tr>
<td><h5>document-id.key-delimiter</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">_</td>
<td>String</td>
- <td>Delimiter for composite keys ("_" by default), e.g., "$" would
result in IDs "KEY1$KEY2$KEY3"."</td>
+ <td>复合键的分隔符（默认为"_"），例如，指定为"$"将导致文档 ID 为"KEY1$KEY2$KEY3"。</td>
</tr>
<tr>
<td><h5>username</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Username used to connect to Elasticsearch instance. Please notice
that Elasticsearch doesn't pre-bundled security feature, but you can enable it
by following the <a
href="https://www.elastic.co/guide/en/elasticsearch/reference/master/configuring-security.html";>guideline</a>
to secure an Elasticsearch cluster.</td>
+ <td>用于连接 Elasticsearch 实例的用户名。请注意，Elasticsearch 没有预绑定安全特性，但你可以通过如下<a
href="https://www.elastic.co/guide/en/elasticsearch/reference/master/configuring-security.html";>指南</a>启用它来保护
Elasticsearch 集群。</td>
</tr>
<tr>
<td><h5>password</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Password used to connect to Elasticsearch instance. If
<code>username</code> is configured, this option must be configured with
non-empty string as well.</td>
+ <td>用于连接 Elasticsearch
实例的密码。如果配置了<code>username</code>，则此选项也必须配置为非空字符串。</td>
</tr>
<tr>
<td><h5>failure-handler</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">fail</td>
<td>String</td>
- <td>Failure handling strategy in case a request to Elasticsearch fails.
Valid strategies are:
+ <td>对 Elasticsearch 请求失败情况下的失败处理策略。有效策略为：
<ul>
- <li><code>fail</code>: throws an exception if a request fails and thus
causes a job failure.</li>
- <li><code>ignore</code>: ignores failures and drops the request.</li>
- <li><code>retry-rejected</code>: re-adds requests that have failed due
to queue capacity saturation.</li>
- <li>custom class name: for failure handling with a
ActionRequestFailureHandler subclass.</li>
+ <li><code>fail</code>：如果请求失败并因此导致作业失败，则抛出异常。</li>
+ <li><code>ignore</code>：忽略失败并放弃请求。</li>
+ <li><code>retry-rejected</code>：重新添加由于队列容量饱和而失败的请求。</li>
+ <li>自定义类名称：使用 ActionRequestFailureHandler 的子类进行失败处理。</li>
</ul>
</td>
</tr>
<tr>
<td><h5>sink.flush-on-checkpoint</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">true</td>
<td>Boolean</td>
- <td>Flush on checkpoint or not. When disabled, a sink will not wait for
all pending action requests
- to be acknowledged by Elasticsearch on checkpoints. Thus, a sink does
NOT provide any strong
- guarantees for at-least-once delivery of action requests.
+ <td>是否在 checkpoint 时执行 flush。禁用后，在 checkpoint 时 sink 将不会等待所有的 pending
请求被 Elasticsearch 确认。因此，sink 不会为请求的 at-least-once 交付提供任何有力保证。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.max-actions</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">1000</td>
<td>Integer</td>
- <td>Maximum number of buffered actions per bulk request.
- Can be set to <code>'0'</code> to disable it.
+ <td>每个批量请求的最大缓冲操作数。
+ 可以设置为<code>'0'</code>来禁用它。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.max-size</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">2mb</td>
<td>MemorySize</td>
- <td>Maximum size in memory of buffered actions per bulk request. Must be
in MB granularity.
- Can be set to <code>'0'</code> to disable it.
+ <td>每个批量请求的缓冲操作在内存中的最大值。单位必须为 MB。
+ 可以设置为<code>'0'</code>来禁用它。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.interval</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">1s</td>
<td>Duration</td>
- <td>The interval to flush buffered actions.
- Can be set to <code>'0'</code> to disable it. Note, both
<code>'sink.bulk-flush.max-size'</code> and
<code>'sink.bulk-flush.max-actions'</code>
- can be set to <code>'0'</code> with the flush interval set allowing
for complete async processing of buffered actions.
+ <td>flush 缓冲操作的间隔。
+
可以设置为<code>'0'</code>来禁用它。注意，<code>'sink.bulk-flush.max-size'</code>和<code>'sink.bulk-flush.max-actions'</code>都设置为<code>'0'</code>的这种
flush 间隔设置允许对缓冲操作进行完全异步处理。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.backoff.strategy</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">DISABLED</td>
<td>String</td>
- <td>Specify how to perform retries if any flush actions failed due to a
temporary request error. Valid strategies are:
+ <td>指定在由于临时请求错误导致任何 flush 操作失败时如何执行重试。有效策略为：
<ul>
- <li><code>DISABLED</code>: no retry performed, i.e. fail after the
first request error.</li>
- <li><code>CONSTANT</code>: wait for backoff delay between retries.</li>
- <li><code>EXPONENTIAL</code>: initially wait for backoff delay and
increase exponentially between retries.</li>
+ <li><code>DISABLED</code>：不执行重试，即第一次请求错误后失败。</li>
+ <li><code>CONSTANT</code>：等待重试之间的回退延迟。</li>
+ <li><code>EXPONENTIAL</code>：先等待回退延迟，然后在重试之间指数递增。</li>
</ul>
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.backoff.max-retries</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">8</td>
<td>Integer</td>
- <td>Maximum number of backoff retries.</td>
+ <td>最大回退重试次数。</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.backoff.delay</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">50ms</td>
<td>Duration</td>
- <td>Delay between each backoff attempt. For <code>CONSTANT</code>
backoff, this is simply the delay between each retry. For
<code>EXPONENTIAL</code> backoff, this is the initial base delay.</td>
+ <td>每次回退尝试之间的延迟。<code>CONSTANT</code>
回退只是每次重试之间的延迟。<code>EXPONENTIAL</code> 回退是初始基准延迟。</td>
Review comment:
```suggestion
<td>每次回退尝试之间的延迟。对于<code>CONSTANT</code> 回退策略，
该值是每次重试之间的延迟。对于<code>EXPONENTIAL</code> 回退策略，该值是初始的延迟。</td>
```
##########
File path: docs/content.zh/docs/connectors/table/elasticsearch.md
##########
@@ -59,212 +59,208 @@ CREATE TABLE myUserTable (
);
```
-Connector Options
+连接器选项
----------------
<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>
+ <th class="text-left" style="width: 25%">选项</th>
+ <th class="text-center" style="width: 8%">是否必选</th>
+ <th class="text-center" style="width: 7%">默认值</th>
+ <th class="text-center" style="width: 10%">类型</th>
+ <th class="text-center" style="width: 50%">描述</th>
</tr>
</thead>
<tbody>
<tr>
<td><h5>connector</h5></td>
- <td>required</td>
+ <td>必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Specify what connector to use, valid values are:
+ <td>指定要使用的连接器，有效值为：
<ul>
- <li><code>elasticsearch-6</code>: connect to Elasticsearch 6.x
cluster</li>
- <li><code>elasticsearch-7</code>: connect to Elasticsearch 7.x and later
versions cluster</li>
+ <li><code>elasticsearch-6</code>：连接到 Elasticsearch 6.x 的集群。</li>
+ <li><code>elasticsearch-7</code>：连接到 Elasticsearch 7.x 及更高版本的集群。</li>
</ul></td>
</tr>
<tr>
<td><h5>hosts</h5></td>
- <td>required</td>
+ <td>必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>One or more Elasticsearch hosts to connect to, e.g.
<code>'http://host_name:9092;http://host_name:9093'</code>.</td>
+ <td>要连接到的一台或多台 Elasticsearch 主机，例如
<code>'http://host_name:9092;http://host_name:9093'</code>。</td>
</tr>
<tr>
<td><h5>index</h5></td>
- <td>required</td>
+ <td>必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Elasticsearch index for every record. Can be a static index (e.g.
<code>'myIndex'</code>) or
- a dynamic index (e.g. <code>'index-{log_ts|yyyy-MM-dd}'</code>).
- See the following <a href="#dynamic-index">Dynamic Index</a> section
for more details.</td>
+ <td>Elasticsearch 中每条记录的索引。可以是一个静态索引（例如
<code>'myIndex'</code>）或一个动态索引（例如 <code>'index-{log_ts|yyyy-MM-dd}'</code>）。
+ 更多详细信息，请参见下面的<a href="#动态索引">动态索引</a>部分。</td>
</tr>
<tr>
<td><h5>document-type</h5></td>
- <td>required in 6.x</td>
+ <td>6.x 版本中必选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Elasticsearch document type. Not necessary anymore in
<code>elasticsearch-7</code>.</td>
+ <td>Elasticsearch 文档类型。在 <code>elasticsearch-7</code> 中不再需要。</td>
</tr>
<tr>
<td><h5>document-id.key-delimiter</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">_</td>
<td>String</td>
- <td>Delimiter for composite keys ("_" by default), e.g., "$" would
result in IDs "KEY1$KEY2$KEY3"."</td>
+ <td>复合键的分隔符（默认为"_"），例如，指定为"$"将导致文档 ID 为"KEY1$KEY2$KEY3"。</td>
</tr>
<tr>
<td><h5>username</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Username used to connect to Elasticsearch instance. Please notice
that Elasticsearch doesn't pre-bundled security feature, but you can enable it
by following the <a
href="https://www.elastic.co/guide/en/elasticsearch/reference/master/configuring-security.html";>guideline</a>
to secure an Elasticsearch cluster.</td>
+ <td>用于连接 Elasticsearch 实例的用户名。请注意，Elasticsearch 没有预绑定安全特性，但你可以通过如下<a
href="https://www.elastic.co/guide/en/elasticsearch/reference/master/configuring-security.html";>指南</a>启用它来保护
Elasticsearch 集群。</td>
</tr>
<tr>
<td><h5>password</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Password used to connect to Elasticsearch instance. If
<code>username</code> is configured, this option must be configured with
non-empty string as well.</td>
+ <td>用于连接 Elasticsearch
实例的密码。如果配置了<code>username</code>，则此选项也必须配置为非空字符串。</td>
</tr>
<tr>
<td><h5>failure-handler</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">fail</td>
<td>String</td>
- <td>Failure handling strategy in case a request to Elasticsearch fails.
Valid strategies are:
+ <td>对 Elasticsearch 请求失败情况下的失败处理策略。有效策略为：
<ul>
- <li><code>fail</code>: throws an exception if a request fails and thus
causes a job failure.</li>
- <li><code>ignore</code>: ignores failures and drops the request.</li>
- <li><code>retry-rejected</code>: re-adds requests that have failed due
to queue capacity saturation.</li>
- <li>custom class name: for failure handling with a
ActionRequestFailureHandler subclass.</li>
+ <li><code>fail</code>：如果请求失败并因此导致作业失败，则抛出异常。</li>
+ <li><code>ignore</code>：忽略失败并放弃请求。</li>
+ <li><code>retry-rejected</code>：重新添加由于队列容量饱和而失败的请求。</li>
+ <li>自定义类名称：使用 ActionRequestFailureHandler 的子类进行失败处理。</li>
</ul>
</td>
</tr>
<tr>
<td><h5>sink.flush-on-checkpoint</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">true</td>
<td>Boolean</td>
- <td>Flush on checkpoint or not. When disabled, a sink will not wait for
all pending action requests
- to be acknowledged by Elasticsearch on checkpoints. Thus, a sink does
NOT provide any strong
- guarantees for at-least-once delivery of action requests.
+ <td>是否在 checkpoint 时执行 flush。禁用后，在 checkpoint 时 sink 将不会等待所有的 pending
请求被 Elasticsearch 确认。因此，sink 不会为请求的 at-least-once 交付提供任何有力保证。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.max-actions</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">1000</td>
<td>Integer</td>
- <td>Maximum number of buffered actions per bulk request.
- Can be set to <code>'0'</code> to disable it.
+ <td>每个批量请求的最大缓冲操作数。
+ 可以设置为<code>'0'</code>来禁用它。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.max-size</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">2mb</td>
<td>MemorySize</td>
- <td>Maximum size in memory of buffered actions per bulk request. Must be
in MB granularity.
- Can be set to <code>'0'</code> to disable it.
+ <td>每个批量请求的缓冲操作在内存中的最大值。单位必须为 MB。
+ 可以设置为<code>'0'</code>来禁用它。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.interval</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">1s</td>
<td>Duration</td>
- <td>The interval to flush buffered actions.
- Can be set to <code>'0'</code> to disable it. Note, both
<code>'sink.bulk-flush.max-size'</code> and
<code>'sink.bulk-flush.max-actions'</code>
- can be set to <code>'0'</code> with the flush interval set allowing
for complete async processing of buffered actions.
+ <td>flush 缓冲操作的间隔。
+
可以设置为<code>'0'</code>来禁用它。注意，<code>'sink.bulk-flush.max-size'</code>和<code>'sink.bulk-flush.max-actions'</code>都设置为<code>'0'</code>的这种
flush 间隔设置允许对缓冲操作进行完全异步处理。
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.backoff.strategy</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">DISABLED</td>
<td>String</td>
- <td>Specify how to perform retries if any flush actions failed due to a
temporary request error. Valid strategies are:
+ <td>指定在由于临时请求错误导致任何 flush 操作失败时如何执行重试。有效策略为：
<ul>
- <li><code>DISABLED</code>: no retry performed, i.e. fail after the
first request error.</li>
- <li><code>CONSTANT</code>: wait for backoff delay between retries.</li>
- <li><code>EXPONENTIAL</code>: initially wait for backoff delay and
increase exponentially between retries.</li>
+ <li><code>DISABLED</code>：不执行重试，即第一次请求错误后失败。</li>
+ <li><code>CONSTANT</code>：等待重试之间的回退延迟。</li>
+ <li><code>EXPONENTIAL</code>：先等待回退延迟，然后在重试之间指数递增。</li>
</ul>
</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.backoff.max-retries</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">8</td>
<td>Integer</td>
- <td>Maximum number of backoff retries.</td>
+ <td>最大回退重试次数。</td>
</tr>
<tr>
<td><h5>sink.bulk-flush.backoff.delay</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">50ms</td>
<td>Duration</td>
- <td>Delay between each backoff attempt. For <code>CONSTANT</code>
backoff, this is simply the delay between each retry. For
<code>EXPONENTIAL</code> backoff, this is the initial base delay.</td>
+ <td>每次回退尝试之间的延迟。<code>CONSTANT</code>
回退只是每次重试之间的延迟。<code>EXPONENTIAL</code> 回退是初始基准延迟。</td>
</tr>
<tr>
<td><h5>connection.max-retry-timeout</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>Duration</td>
- <td>Maximum timeout between retries.</td>
+ <td>最大重试超时时间。</td>
</tr>
<tr>
<td><h5>connection.path-prefix</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">(none)</td>
<td>String</td>
- <td>Prefix string to be added to every REST communication, e.g.,
<code>'/v1'</code></td>
+ <td>添加到每个 REST 通信中的前缀字符串，例如，<code>'/v1'</code>。</td>
</tr>
<tr>
<td><h5>format</h5></td>
- <td>optional</td>
+ <td>可选</td>
<td style="word-wrap: break-word;">json</td>
<td>String</td>
- <td>Elasticsearch connector supports to specify a format. The format
must produce a valid json document.
- By default uses built-in <code>'json'</code> format. Please refer to <a
href="{{< ref "docs/connectors/table/formats/overview" >}}">JSON Format</a>
page for more details.
+ <td>Elasticsearch 连接器支持指定格式。该格式必须生成一个有效的 json 文档。
+ 默认使用内置的 <code>'json'</code> 格式。更多详细信息，请参阅 <a href="{{< ref
"docs/connectors/table/formats/overview" >}}">JSON Format</a> 页面。
</td>
</tr>
</tbody>
</table>
-Features
+特性
----------------
-### Key Handling
+### Key 处理
-Elasticsearch sink can work in either upsert mode or append mode, it depends
on whether primary key is defined.
-If primary key is defined, Elasticsearch sink works in upsert mode which can
consume queries containing UPDATE/DELETE messages.
-If primary key is not defined, Elasticsearch sink works in append mode which
can only consume queries containing INSERT only messages.
+Elasticsearch sink 可以根据是否定义了主键来确定是在 upsert 模式还是 append 模式下工作。
+如果定义了主键，Elasticsearch sink 将以 upsert 模式工作，该模式可以消费包含 UPDATE/DELETE 消息的查询。
+如果未定义主键，Elasticsearch sink 将以 append 模式工作，该模式只能消费包含 INSERT 消息的查询。
-In Elasticsearch connector, the primary key is used to calculate the
Elasticsearch document id, which is a string of up to 512 bytes. It cannot have
whitespaces.
-The Elasticsearch connector generates a document ID string for every row by
concatenating all primary key fields in the order defined in the DDL using a
key delimiter specified by `document-id.key-delimiter`.
-Certain types are not allowed as primary key field as they do not have a good
string representation, e.g. `BYTES`, `ROW`, `ARRAY`, `MAP`, etc.
-If no primary key is specified, Elasticsearch will generate a document id
automatically.
+在 Elasticsearch 连接器中，主键用于计算 Elasticsearch 的文档 id，文档 id 为最多 512 字节且不包含空格的字符串。
+Elasticsearch 连接器通过使用 `document-id.key-delimiter` 指定的键分隔符按照 DDL
中定义的顺序连接所有主键字段，为每一行生成一个文档 ID 字符串。
Review comment:
每一行记录
--
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]
