swuferhong commented on code in PR #3257:
URL: https://github.com/apache/fluss/pull/3257#discussion_r3347623557
##########
website/docs/engine-flink/options.md:
##########
@@ -91,7 +92,7 @@ See more details about [ALTER TABLE ...
SET](engine-flink/ddl.md#set-properties)
| table.delete.behavior | Enum | ALLOW
| Controls the behavior of delete operations on primary key tables.
Three modes are supported: `ALLOW` (default for default merge engine) - allows
normal delete operations; `IGNORE` - silently ignores delete requests without
errors; `DISABLE` - rejects delete requests and throws explicit errors. This
configuration provides system-level guarantees for some downstream pipelines
(e.g., Flink Delta Join) that must not receive any delete events in the
changelog of the table. For tables with `first_row` or `versioned` or
`aggregation` merge engines, this option is automatically set to `IGNORE` and
cannot be overridden. Note: For `aggregation` merge engine, when set to
`allow`, delete operations will remove the entire record. This configuration
only applicable to primary key tables.
|
| table.changelog.image | Enum | FULL
| Defines the changelog image mode for primary key tables. This
configuration is inspired by similar settings in database systems like MySQL's
`binlog_row_image` and PostgreSQL's `replica identity`. Two modes are
supported: `FULL` (default) - produces both UPDATE_BEFORE and UPDATE_AFTER
records for update operations, capturing complete information about updates and
allowing tracking of previous values; `WAL` - does not produce UPDATE_BEFORE
records. Only INSERT, UPDATE_AFTER (and DELETE if allowed) records are emitted.
When WAL mode is enabled, the default merge engine is used (no merge engine
configured), updates are full row updates (not partial update), and there is no
auto-increment column, an optimization is applied to skip looking up old
values, and in this case INSERT operations are converted to UPDATE_AFTER
events. This mode reduces storage and transmission costs but loses the ability
to track previous values. Only applicable to primary key tables.
|
| table.auto-inc.batch-size | Long | 100000L
| The batch size of auto-increment IDs fetched from the distributed
counter each time. This value determines the length of the locally cached ID
segment. Default: 100000. A larger batch size may cause significant
auto-increment ID gaps, especially when unused cached ID segments are discarded
due to TabletServer restarts or abnormal terminations. Conversely, a smaller
batch size increases the frequency of ID fetch requests to the distributed
counter, introducing extra network overhead and reducing write throughput and
performance.
|
-| table.statistics.columns | String | (None)
| Configures column-level statistics collection for the table. By
default this option is not set and no column statistics are collected. The
value `*` means collect statistics for all supported columns. A comma-separated
list of column names means collect statistics only for the specified columns
(recommended for minimal overhead). Supported types: BOOLEAN, TINYINT,
SMALLINT, INTEGER, BIGINT, FLOAT, DOUBLE, STRING, CHAR, DECIMAL, DATE, TIME,
TIMESTAMP, TIMESTAMP_LTZ. Unsupported types (BYTES, BINARY, ARRAY, MAP, ROW)
are automatically excluded. Example: `'col1,col2'` to collect statistics only
for columns used in filter conditions. Note: enabling column statistics
requires the V1 batch format. Downstream consumers must be upgraded to Fluss
v1.0+ before enabling this option. |
+| table.statistics.columns | String | (None)
| Configures column-level statistics collection for the table. By
default this option is not set and no column statistics are collected. The
value `*` means collect statistics for all supported columns. A comma-separated
list of column names means collect statistics only for the specified columns
(recommended for minimal overhead). Supported types: BOOLEAN, TINYINT,
SMALLINT, INTEGER, BIGINT, FLOAT, DOUBLE, STRING, CHAR, DECIMAL, DATE, TIME,
TIMESTAMP, TIMESTAMP_LTZ. Unsupported types (BYTES, BINARY, ARRAY, MAP, ROW)
are automatically excluded. Example: `'col1,col2'` to collect statistics only
for columns used in filter conditions. Note: enabling column statistics
requires the V1 batch format. Downstream consumers must be upgraded to Fluss
v1.0+ before enabling this option.
|
Review Comment:
just fix the check style problem of md file
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
