This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
The following commit(s) were added to refs/heads/master by this push:
new c4ceb1fe17 [INLONG-783][Doc][HDFS] Describe tables using MarkDown
(#787)
c4ceb1fe17 is described below
commit c4ceb1fe17f04684f2bfc04def78d28c8233ad93
Author: emhui <[email protected]>
AuthorDate: Wed Jun 28 15:15:20 2023 +0800
[INLONG-783][Doc][HDFS] Describe tables using MarkDown (#787)
---
docs/data_node/load_node/hdfs.md | 186 ++++-----------------
.../current/data_node/load_node/hdfs.md | 182 ++++----------------
2 files changed, 65 insertions(+), 303 deletions(-)
diff --git a/docs/data_node/load_node/hdfs.md b/docs/data_node/load_node/hdfs.md
index 11da0bc95e..781d3cffa3 100644
--- a/docs/data_node/load_node/hdfs.md
+++ b/docs/data_node/load_node/hdfs.md
@@ -33,132 +33,50 @@ CREATE TABLE hdfs_load_node (
```
#### File Formats
-<ul>
-<li>CSV(Uncompressed)</li>
-<li>JSON(JSON format for file system connector is not a typical JSON file but
uncompressed newline delimited JSON.)</li>
-<li>Avro(Support compression by configuring avro.codec.)</li>
-<li>Parquet(Compatible with Hive.)</li>
-<li>Orc(Compatible with Hive.)</li>
-<li>Debezium-JSON</li>
-<li>Canal-JSON</li>
-<li>Raw</li>
-</ul>
+
+- CSV(Uncompressed)
+- JSON(JSON format for file system connector is not a typical JSON file but
uncompressed newline delimited JSON.)
+- Avro(Support compression by configuring avro.codec.)
+- Parquet(Compatible with Hive.)
+- Orc(Compatible with Hive.)
+- Debezium-JSON
+- Canal-JSON
+- Raw
#### Rolling Policy
Data within the partition directories are split into part files.
Each partition will contain at least one part file for each subtask of the
sink that has received data for that partition.
The in-progress part file will be closed and additional part file will be
created according to the configurable rolling policy.
The policy rolls part files based on size, a timeout that specifies the
maximum duration for which a file can be open.
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '25%'}}>Option</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>sink.rolling-policy.file-size</h5></td>
- <td style={{wordWrap: 'break-word'}}>128MB</td>
- <td>MemorySize</td>
- <td>The maximum part file size before rolling.</td>
- </tr>
- <tr>
- <td><h5>sink.rolling-policy.rollover-interval</h5></td>
- <td style={{wordWrap: 'break-word'}}>30 min</td>
- <td>String</td>
- <td>The maximum time duration a part file can stay open before rolling
(by default 30 min to avoid to many small files). The frequency at which this
is checked is controlled by the 'sink.rolling-policy.check-interval'
option.</td>
- </tr>
- <tr>
- <td><h5>sink.rolling-policy.check-interval</h5></td>
- <td style={{wordWrap: 'break-word'}}>1 min</td>
- <td>String</td>
- <td>The interval for checking time based rolling policies. This controls
the frequency to check whether a part file should rollover based on
'sink.rolling-policy.rollover-interval'.</td>
- </tr>
- </tbody>
-</table>
+
+| Option | Default | Type | Description |
+| --- | --- | --- | --- |
+| sink.rolling-policy.file-size | 128MB | MemorySize | The maximum part file
size before rolling. |
+| sink.rolling-policy.rollover-interval | 30 min | String | The maximum time
duration a part file can stay open before rolling (by default 30 min to avoid
to many small files). The frequency at which this is checked is controlled by
the 'sink.rolling-policy.check-interval' option. |
+| sink.rolling-policy.check-interval | 1 min | String | The interval for
checking time based rolling policies. This controls the frequency to check
whether a part file should rollover based on
'sink.rolling-policy.rollover-interval'. |
#### File Compaction
+
The file sink supports file compactions, which allows applications to have
smaller checkpoint intervals without generating a large number of files.
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '25%'}}>Option</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>auto-compaction</h5></td>
- <td style={{wordWrap: 'break-word'}}>false</td>
- <td>Boolean</td>
- <td>Whether to enable automatic compaction in streaming sink or not.
- The data will be written to temporary files. After the checkpoint is
completed, the temporary files generated by a checkpoint will be compacted.
- The temporary files are invisible before compaction.</td>
- </tr>
- <tr>
- <td><h5>compaction.file-size</h5></td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>The compaction target file size, the default value is the rolling
file size.</td>
- </tr>
- <tr>
- <td>inlong.metric.labels</td>
- <td>optional</td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>Inlong metric label, format of value is
groupId=[groupId]&streamId=[streamId]&nodeId=[nodeId].</td>
- </tr>
- </tbody>
-</table>
+
+| Option | Default | Type | Description |
+| --- | --- | --- | --- |
+| auto-compaction | false | Boolean | Whether to enable automatic compaction
in streaming sink or not. The data will be written to temporary files. After
the checkpoint is completed, the temporary files generated by a checkpoint will
be compacted. The temporary files are invisible before compaction. |
+| compaction.file-size | (none) | String | The compaction target file size,
the default value is the rolling file size. |
+| inlong.metric.labels | (none) | String | Inlong metric label, format of
value is groupId=[groupId]&streamId=[streamId]&nodeId=[nodeId]. |
#### Partition Commit
+
After writing a partition, it is often necessary to notify downstream
applications.
For example, add the partition to a Hive metastore or writing a _SUCCESS file
in the directory.
The file system sink contains a partition commit feature that allows
configuring custom policies.
Commit actions are based on a combination of triggers and policies.
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '25%'}}>Option</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>sink.partition-commit.trigger</h5></td>
- <td style={{wordWrap: 'break-word'}}>process-time</td>
- <td>String</td>
- <td>Trigger type for partition commit: 'process-time': based on the
time of the machine, it neither requires partition time extraction nor
watermark generation. Commit partition once the 'current system time' passes
'partition creation system time' plus 'delay'. 'partition-time': based on the
time that extracted from partition values, it requires watermark generation.
Commit partition once the 'watermark' passes 'time extracted from partition
values' plus 'delay'.</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.delay</h5></td>
- <td style={{wordWrap: 'break-word'}}>0 s</td>
- <td>Duration</td>
- <td>The partition will not commit until the delay time. If it is a daily
partition, should be '1 d', if it is a hourly partition, should be '1 h'.</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.watermark-time-zone</h5></td>
- <td style={{wordWrap: 'break-word'}}>UTC</td>
- <td>String</td>
- <td>The time zone to parse the long watermark value to TIMESTAMP value,
- the parsed watermark timestamp is used to compare with partition time
to decide the partition should commit or not.
- This option is only take effect when `sink.partition-commit.trigger` is
set to 'partition-time'.
- If this option is not configured correctly, e.g.
- source rowtime is defined on TIMESTAMP_LTZ column, but this config is
not configured,
- then users may see the partition committed after a few hours. The
default value is 'UTC',
- which means the watermark is defined on TIMESTAMP column or not
defined.
- If the watermark is defined on TIMESTAMP_LTZ column, the time zone of
watermark is the session time zone.
- The option value is either a full name such as 'America/Los_Angeles',
or a custom timezone id such as 'GMT-08:00'.</td>
- </tr>
- </tbody>
-</table>
+
+| Option | Default | Type | Description |
+| --- | --- | --- | --- |
+| sink.partition-commit.trigger | process-time | String | Trigger type for
partition commit: 'process-time': based on the time of the machine, it neither
requires partition time extraction nor watermark generation. Commit partition
once the 'current system time' passes 'partition creation system time' plus
'delay'. 'partition-time': based on the time that extracted from partition
values, it requires watermark generation. Commit partition once the 'watermark'
passes 'time extracted from [...]
+| sink.partition-commit.delay | 0 s | Duration | The partition will not
commit until the delay time. If it is a daily partition, should be '1 d', if it
is a hourly partition, should be '1 h'. |
+| sink.partition-commit.watermark-time-zone | UTC | String | The time zone to
parse the long watermark value to TIMESTAMP value, the parsed watermark
timestamp is used to compare with partition time to decide the partition should
commit or not. This option is only take effect when
\`sink.partition-commit.trigger\` is set to 'partition-time'. If this option is
not configured correctly, e.g. source rowtime is defined on TIMESTAMP\_LTZ
column, but this config is not configured, then users [...]
#### Partition Commit Policy
@@ -168,44 +86,8 @@ The partition strategy defines the specific operation of
partition submission.
- metastore：This strategy is only supported when hive.
- success: The '_SUCCESS' file will be generated after the part file is
generated.
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '25%'}}>Option</th>
- <th class="text-left" 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>sink.partition-commit.policy.kind</h5></td>
- <td>optional</td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>Policy to commit a partition is to notify the downstream
application that the partition has finished writing, the partition is ready to
be read.
- metastore: add partition to metastore. Only hive table supports
metastore policy,
- file system manages partitions through directory structure.
success-file: add '_success' file to directory.
- Both can be configured at the same time: 'metastore,success-file'.
custom: use policy class to create a commit policy.
- Support to configure multiple policies: 'metastore,success-file'.</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.policy.class</h5></td>
- <td>optional</td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>The partition commit policy class for implement
PartitionCommitPolicy interface.
- Only work in custom commit policy.</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.success-file.name</h5></td>
- <td>optional</td>
- <td style={{wordWrap: 'break-word'}}>_SUCCESS</td>
- <td>String</td>
- <td>The file name for success-file partition commit policy, default is
'_SUCCESS'.</td>
- </tr>
- </tbody>
-</table>
-
-
+| Option | Required | Default | Type | Description |
+| --- | --- | --- | --- | --- |
+| sink.partition-commit.policy.kind | optional | (none) | String | Policy to
commit a partition is to notify the downstream application that the partition
has finished writing, the partition is ready to be read. metastore: add
partition to metastore. Only hive table supports metastore policy, file system
manages partitions through directory structure. success-file: add '_success'
file to directory. Both can be configured at the same time:
'metastore,success-file'. custom: use policy cla [...]
+| sink.partition-commit.policy.class | optional | (none) | String | The
partition commit policy class for implement PartitionCommitPolicy interface.
Only work in custom commit policy. |
+| sink.partition-commit.success-file.name | optional | _SUCCESS | String | The
file name for success-file partition commit policy, default is '_SUCCESS'. |
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data_node/load_node/hdfs.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data_node/load_node/hdfs.md
index f8d212c59d..264abd412e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data_node/load_node/hdfs.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data_node/load_node/hdfs.md
@@ -32,16 +32,15 @@ CREATE TABLE hdfs_load_node (
```
#### File Formats
-<ul>
-<li>CSV(非压缩格式)</li>
-<li>JSON(文件系统连接器的 JSON format 与传统的标准的 JSON file 的不同，而是非压缩的。换行符分割的 JSON)</li>
-<li>Avro(通过配置 avro.codec 属性支持压缩)</li>
-<li>Parquet(与 hive 兼容)</li>
-<li>Orc(与 hive 兼容)</li>
-<li>Debezium-JSON</li>
-<li>Canal-JSON</li>
-<li>Raw</li>
-</ul>
+
+- CSV(非压缩格式)
+- JSON(文件系统连接器的 JSON format 与传统的标准的 JSON file 的不同，而是非压缩的。换行符分割的 JSON)
+- Avro(通过配置 avro.codec 属性支持压缩)
+- Parquet(与 hive 兼容)
+- Orc(与 hive 兼容)
+- Debezium-JSON
+- Canal-JSON
+- Raw
备注：文件格式明细可以查看[Flink
Formats](https://nightlies.apache.org/flink/flink-docs-master/zh/docs/connectors/table/formats/overview/)
@@ -50,73 +49,21 @@ CREATE TABLE hdfs_load_node (
数据会被加载到文件的目录下的 part 文件中，每个分区接收到来之 subtask 的数据至少会为该分区生成一个 part 文件。同时可以配置滚动策略
来生成 part 文件，生成 part 文件会将 in-progress part 文件关闭。该策略基于大小和指定文件被打开的超时时间来生成 part 文件。
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '10%'}}>参数</th>
- <th class="text-left" style={{width: '7%'}}>默认值</th>
- <th class="text-left" style={{width: '10%'}}>数据类型</th>
- <th class="text-left" style={{width: '65%'}}>描述</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><h5>sink.rolling-policy.file-size</h5></td>
- <td style={{wordWrap: 'break-word'}}>128MB</td>
- <td>MemorySize</td>
- <td>滚动前 part 文件的最大值。</td>
- </tr>
- <tr>
- <td><h5>sink.rolling-policy.rollover-interval</h5></td>
- <td style={{wordWrap: 'break-word'}}>30 min</td>
- <td>String</td>
- <td>滚动前，part 文件处于打开状态的最大时长（默认值30分钟，以避免产生大量小文件）。
- 检查频率是由 'sink.rolling-policy.check-interval' 属性控制的。</td>
- </tr>
- <tr>
- <td><h5>sink.rolling-policy.check-interval</h5></td>
- <td style={{wordWrap: 'break-word'}}>1 min</td>
- <td>String</td>
- <td>基于时间的滚动策略的检查间隔。
- 该属性控制了基于 'sink.rolling-policy.rollover-interval' 属性检查文件是否该被滚动的检查频率。</td>
- </tr>
- </tbody>
-</table>
+| 参数 | 默认值 | 数据类型 | 描述 |
+| --- | --- | --- | --- |
+| sink.rolling-policy.file-size | 128MB | MemorySize | 滚动前 part 文件的最大值。 |
+| sink.rolling-policy.rollover-interval | 30 min | String | 滚动前，part
文件处于打开状态的最大时长（默认值30分钟，以避免产生大量小文件）。 检查频率是由 'sink.rolling-policy.check-interval'
属性控制的。 |
+| sink.rolling-policy.check-interval | 1 min | String | 基于时间的滚动策略的检查间隔。
该属性控制了基于 'sink.rolling-policy.rollover-interval' 属性检查文件是否该被滚动的检查频率。 |
#### 文件合并
+
支持文件能力，允许在较小的 checkpoint 下不产生大量的小文件。
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '10%'}}>参数</th>
- <th class="text-left" style={{width: '7%'}}>默认值</th>
- <th class="text-left" style={{width: '10%'}}>数据类型</th>
- <th class="text-left" style={{width: '65%'}}>描述</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><h5>auto-compaction</h5></td>
- <td style={{wordWrap: 'break-word'}}>false</td>
- <td>Boolean</td>
- <td>在流式 sink 中是否开启自动合并功能，数据首先会被写入临时文件。
- 当 checkpoint 完成后，该检查点产生的临时文件会被合并，这些临时文件在合并前不可见。</td>
- </tr>
- <tr>
- <td><h5>compaction.file-size</h5></td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>合并目标文件大小，默认值为滚动文件大小。</td>
- </tr>
- <tr>
- <td>inlong.metric.labels</td>
- <td>可选</td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>inlong metric
的标签值，该值的构成为groupId=[groupId]&streamId=[streamId]&nodeId=[nodeId]。</td>
- </tr>
- </tbody>
-</table>
+
+| 参数 | 默认值 | 数据类型 | 描述
|
+| --- | --- | ---
|------------------------------------------------------------------------------------|
+| auto-compaction | false | Boolean | 在流式 sink 中是否开启自动合并功能，数据首先会被写入临时文件。 当
checkpoint 完成后，该检查点产生的临时文件会被合并，这些临时文件在合并前不可见。 |
+| compaction.file-size | (none) | String | 合并目标文件大小，默认值为滚动文件大小。
|
+| inlong.metric.labels | (none) | String | inlong metric 的标签值，该值的构成为
groupId=g[groupId]&streamId=[streamId]&nodeId=[nodeId]。 |
#### 分区提交
@@ -128,45 +75,11 @@ CREATE TABLE hdfs_load_node (
备注：分区提交仅支持动态分区插入。
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '10%'}}>参数</th>
- <th class="text-left" style={{width: '7%'}}>默认值</th>
- <th class="text-left" style={{width: '10%'}}>数据类型</th>
- <th class="text-left" style={{width: '65%'}}>描述</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><h5>sink.partition-commit.trigger</h5></td>
- <td style={{wordWrap: 'break-word'}}>process-time</td>
- <td>String</td>
- <td>分区提交触发器类型： 'process-time'：基于机器时间既不需要分区时间提取器也不需要 watermark 生成器。
- 一旦 "当前系统时间" 超过了 "分区创建系统时间" 和 'sink.partition-commit.delay'
之和立即提交分区。<br/>
- 'partition-time'：基于提取的分区时间，需要 watermark 生成。一旦 watermark 超过了
"分区创建系统时间" 和 'sink.partition-commit.delay' 之和立即提交分区。</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.delay</h5></td>
- <td style={{wordWrap: 'break-word'}}>0 s</td>
- <td>Duration</td>
- <td>如果设置分区延迟提交，这个延迟时间之前不会提交。天：'d'；小时：'h';秒：'s'等</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.watermark-time-zone</h5></td>
- <td style={{wordWrap: 'break-word'}}>UTC</td>
- <td>String</td>
- <td> 解析 Long 类型的 watermark 到 TIMESTAMP 类型时所采用的时区，
- 解析得到的 watermark 的 TIMESTAMP 会被用来跟分区时间进行比较以判断是否该被提交。
- 这个属性仅当 `sink.partition-commit.trigger` 被设置为 'partition-time' 时有效。
- 如果这个属性设置的不正确，例如在 TIMESTAMP_LTZ 类型的列上定义了 source rowtime，
- 如果没有设置该属性，那么用户可能会在若干个小时后才看到分区的提交。
- 默认值为 'UTC' 意味着 watermark 是定义在 TIMESTAMP 类型的列上或者没有定义 watermark。
- 如果 watermark 定义在 TIMESTAMP_LTZ 类型的列上，watermark 时区必须是会话时区（session time
zone）。
- 该属性的可选值要么是完整的时区名比如 'America/Los_Angeles'，要么是自定义时区，例如 'GMT-08:00'。</td>
- </tr>
- </tbody>
-</table>
+| 参数 | 默认值 | 数据类型 | 描述 |
+| --- | --- | --- | --- |
+| sink.partition-commit.trigger | process-time | String | 分区提交触发器类型：
'process-time'：基于机器时间既不需要分区时间提取器也不需要 watermark 生成器。 一旦 "当前系统时间" 超过了 "分区创建系统时间"
和 'sink.partition-commit.delay' 之和立即提交分区。<br/>'partition-time'：基于提取的分区时间，需要
watermark 生成。一旦 watermark 超过了 "分区创建系统时间" 和 'sink.partition-commit.delay'
之和立即提交分区。 |
+| sink.partition-commit.delay | 0 s | Duration |
如果设置分区延迟提交，这个延迟时间之前不会提交。天：'d'；小时：'h';秒：'s'等 |
+| sink.partition-commit.watermark-time-zone | UTC | String | 解析 Long 类型的
watermark 到 TIMESTAMP 类型时所采用的时区， 解析得到的 watermark 的 TIMESTAMP
会被用来跟分区时间进行比较以判断是否该被提交。 这个属性仅当 \`sink.partition-commit.trigger\` 被设置为
'partition-time' 时有效。 如果这个属性设置的不正确，例如在 TIMESTAMP\_LTZ 类型的列上定义了 source rowtime，
如果没有设置该属性，那么用户可能会在若干个小时后才看到分区的提交。 默认值为 'UTC' 意味着 watermark 是定义在 TIMESTAMP
类型的列上或者没有定义 watermark。 如果 watermark 定义在 TIMESTAMP\_LTZ 类型的列上，watermark
时区必须是会话时区（session time zone）。 该属性的可选值要么是完整的时区名比如 'America/Los_A [...]
#### 分区提交策略
@@ -175,41 +88,8 @@ CREATE TABLE hdfs_load_node (
- metastore：仅在 hive 时支持该策略。
- success: part 文件生成后会生成 '_SUCCESS' 文件。
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style={{width: '25%'}}>参数</th>
- <th class="text-left" 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>sink.partition-commit.policy.kind</h5></td>
- <td>可选</td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>分区策略通知分区 part 生成可以被访问，仅 hive 支持 metastore 策略，文件系统生成 '_success'
文件表示文件写入完成。
- 两种策略的指定分别为 'metastore,success-file' ，也可以通过 custom 的指定的类创建提交策略。</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.policy.class</h5></td>
- <td>可选</td>
- <td style={{wordWrap: 'break-word'}}>(none)</td>
- <td>String</td>
- <td>实现 PartitionCommitPolicy 接口的分区提交策略类，只有在 custom 提交策略下才使用该类。</td>
- </tr>
- <tr>
- <td><h5>sink.partition-commit.success-file.name</h5></td>
- <td>可选</td>
- <td style={{wordWrap: 'break-word'}}>_SUCCESS</td>
- <td>String</td>
- <td>使用 success-file 分区提交策略时的文件名，默认值是 '_SUCCESS'。</td>
- </tr>
- </tbody>
-</table>
-
-
-
+| 参数 | 是否必须 | 默认值 | 数据类型 | 描述 |
+| --- | --- | --- | --- | --- |
+| sink.partition-commit.policy.kind | 可选 | (none) | String | 分区策略通知分区 part
生成可以被访问，仅 hive 支持 metastore 策略，文件系统生成 '_success' 文件表示文件写入完成。 两种策略的指定分别为
'metastore,success-file' ，也可以通过 custom 的指定的类创建提交策略。 |
+| sink.partition-commit.policy.class | 可选 | (none) | String | 实现
PartitionCommitPolicy 接口的分区提交策略类，只有在 custom 提交策略下才使用该类。 |
+| sink.partition-commit.success-file.name | 可选 | _SUCCESS | String | 使用
success-file 分区提交策略时的文件名，默认值是 '_SUCCESS'。 |
\ No newline at end of file
