From 8f2d6003fadef412371690a106c181941eb86398 Mon Sep 17 00:00:00 2001 From: D3Hunter Date: Mon, 28 Apr 2025 12:08:47 +0800 Subject: [PATCH 1/2] change --- sql-statements/sql-statement-import-into.md | 2 +- tidb-configuration-file.md | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/sql-statements/sql-statement-import-into.md b/sql-statements/sql-statement-import-into.md index af96bf76ddf96..359a009635031 100644 --- a/sql-statements/sql-statement-import-into.md +++ b/sql-statements/sql-statement-import-into.md @@ -149,7 +149,7 @@ The supported options are described as follows: | `SKIP_ROWS=` | CSV | Specifies the number of rows to skip. The default value is `0`. You can use this option to skip the header in a CSV file. If you use a wildcard to specify the source files for import, this option applies to all source files that are matched by the wildcard in `fileLocation`. | | `SPLIT_FILE` | CSV | Splits a single CSV file into multiple smaller chunks of around 256 MiB for parallel processing to improve import efficiency. This parameter only works for **non-compressed** CSV files and has the same usage restrictions as that of TiDB Lightning [`strict-format`](https://docs.pingcap.com/tidb/stable/tidb-lightning-data-source#strict-format). Note that you need to explicitly specify `LINES_TERMINATED_BY` for this option. | | `DISK_QUOTA=''` | All file formats | Specifies the disk space threshold that can be used during data sorting. The default value is 80% of the disk space in the TiDB [temporary directory](https://docs.pingcap.com/tidb/stable/tidb-configuration-file#temp-dir-new-in-v630). If the total disk size cannot be obtained, the default value is 50 GiB. When specifying `DISK_QUOTA` explicitly, make sure that the value does not exceed 80% of the disk space in the TiDB temporary directory. | -| `DISABLE_TIKV_IMPORT_MODE` | All file formats | Specifies whether to disable switching TiKV to import mode during the import process. By default, switching TiKV to import mode is not disabled. If there are ongoing read-write operations in the cluster, you can enable this option to avoid impact from the import process. | +| `DISABLE_TIKV_IMPORT_MODE` | All file formats | Specifies whether to disable switching TiKV to import mode during the import process. By default, switching TiKV to import mode is not disabled. If there are ongoing read-write operations in the cluster, you can enable this option to avoid impact from the import process. Since version v9.0.0-xx(next release version), when import using global sort, switching TiKV to import mode is disabled. | | `THREAD=` | All file formats and query results of `SELECT` | Specifies the concurrency for import. For `IMPORT INTO ... FROM FILE`, the default value of `THREAD` is 50% of the number of CPU cores on the TiDB node, the minimum value is `1`, and the maximum value is the number of CPU cores. For `IMPORT INTO ... FROM SELECT`, the default value of `THREAD` is `2`, the minimum value is `1`, and the maximum value is two times the number of CPU cores on the TiDB node. To import data into a new cluster without any data, it is recommended to increase this concurrency appropriately to improve import performance. If the target cluster is already used in a production environment, it is recommended to adjust this concurrency according to your application requirements. | | `MAX_WRITE_SPEED=''` | All file formats | Controls the write speed to a TiKV node. By default, there is no speed limit. For example, you can specify this option as `1MiB` to limit the write speed to 1 MiB/s. | | `CHECKSUM_TABLE=''` | All file formats | Configures whether to perform a checksum check on the target table after the import to validate the import integrity. The supported values include `"required"` (default), `"optional"`, and `"off"`. `"required"` means performing a checksum check after the import. If the checksum check fails, TiDB will return an error and the import will exit. `"optional"` means performing a checksum check after the import. If an error occurs, TiDB will return a warning and ignore the error. `"off"` means not performing a checksum check after the import. | diff --git a/tidb-configuration-file.md b/tidb-configuration-file.md index de85aa3ffa74b..a38b63a6631d9 100644 --- a/tidb-configuration-file.md +++ b/tidb-configuration-file.md @@ -77,6 +77,10 @@ The TiDB configuration file supports more options than command-line parameters. + Default value: `-1` + When the remaining available storage in `tmp-storage-path` is lower than the value defined by `tmp-storage-quota`, the TiDB server reports an error when it is started, and exits. +### `tikv-worker-url` New in v9.0.0-xxxx + ++ Specifies the url of tikv-worker. We added in the code, but it's not used in this version. Please don't use it, this config might be deleted without notifications. + ### `lease` + The timeout of the DDL lease. From 99f7c8f90e098e2f05021a797fd7a1df8794a7ad Mon Sep 17 00:00:00 2001 From: D3Hunter Date: Mon, 28 Apr 2025 12:13:55 +0800 Subject: [PATCH 2/2] Update tidb-configuration-file.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-configuration-file.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-configuration-file.md b/tidb-configuration-file.md index a38b63a6631d9..cd8c6ff027edd 100644 --- a/tidb-configuration-file.md +++ b/tidb-configuration-file.md @@ -79,7 +79,7 @@ The TiDB configuration file supports more options than command-line parameters. ### `tikv-worker-url` New in v9.0.0-xxxx -+ Specifies the url of tikv-worker. We added in the code, but it's not used in this version. Please don't use it, this config might be deleted without notifications. ++ Specifies the url of tikv-worker. This option is added but currently unused and may be removed in a future release without notice. ### `lease`