From e0a89ef75da4826e90cc377819a15f174e18e7f7 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Thu, 27 Nov 2025 11:48:06 +0800 Subject: [PATCH 1/3] Update dumpling-overview.md --- dumpling-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dumpling-overview.md b/dumpling-overview.md index 46a9c05d8b513..7613e34745395 100644 --- a/dumpling-overview.md +++ b/dumpling-overview.md @@ -406,7 +406,7 @@ SET GLOBAL tidb_gc_life_time = '10m'; | `--cert` | The address of the client certificate file for TLS connection | | `--key` | The address of the client private key file for TLS connection | | `--csv-delimiter` | Delimiter of character type variables in CSV files | '"' | -| `--csv-separator` | Separator of each value in CSV files. It is not recommended to use the default ','. It is recommended to use '\|+\|' or other uncommon character combinations| ',' | ',' | +| `--csv-separator` | Separator of each value in CSV files. If the data contains commas, it is recommended to use an uncommon or non-standard character as the delimiter when exporting the source file. Invisible characters are supported as delimiters, for example: `--csv-separator $'\001'`.| ',' | ',' | | `--csv-null-value` | Representation of null values in CSV files | "\\N" | | `--csv-line-terminator` | The terminator at the end of a line for CSV files. When exporting data to a CSV file, you can specify the desired terminator with this option. This option supports "\\r\\n" and "\\n". The default value is "\\r\\n", which is consistent with the earlier versions. Because quotes in bash have different escaping rules, if you want to specify LF (linefeed) as a terminator, you can use a syntax similar to `--csv-line-terminator $'\n'`. | "\\r\\n" | | `--csv-output-dialect` | Indicates that the source data can be exported to a CSV file in a specific required format for the database. The option value can be `""`, `"snowflake"`, `"redshift"`, or `"bigquery"`. The default value is `""`, which means to encode and export the source data according to UTF-8. If you set the option to `"snowflake"` or `"redshift"`, the binary data type in the source data will be converted to hexadecimal, but the `0x` prefix will be removed. For example, `0x61` will be represented as `61`. If you set the option to `"bigquery"`, the binary data type will be encoded using base64. In some cases, the binary strings might contain garbled characters. | `""` | From db3738eff6c02b098fe686b4d13ffba6b316104d Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Thu, 27 Nov 2025 11:52:41 +0800 Subject: [PATCH 2/3] Update dumpling-overview.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- dumpling-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dumpling-overview.md b/dumpling-overview.md index 7613e34745395..2815d0396267f 100644 --- a/dumpling-overview.md +++ b/dumpling-overview.md @@ -406,7 +406,7 @@ SET GLOBAL tidb_gc_life_time = '10m'; | `--cert` | The address of the client certificate file for TLS connection | | `--key` | The address of the client private key file for TLS connection | | `--csv-delimiter` | Delimiter of character type variables in CSV files | '"' | -| `--csv-separator` | Separator of each value in CSV files. If the data contains commas, it is recommended to use an uncommon or non-standard character as the delimiter when exporting the source file. Invisible characters are supported as delimiters, for example: `--csv-separator $'\001'`.| ',' | ',' | +| `--csv-separator` | Separator for each value in CSV files. If your data contains commas, it is recommended to use an uncommon character as the separator. Invisible characters are also supported, for example: `--csv-separator $'\001'`. | ',' | | `--csv-null-value` | Representation of null values in CSV files | "\\N" | | `--csv-line-terminator` | The terminator at the end of a line for CSV files. When exporting data to a CSV file, you can specify the desired terminator with this option. This option supports "\\r\\n" and "\\n". The default value is "\\r\\n", which is consistent with the earlier versions. Because quotes in bash have different escaping rules, if you want to specify LF (linefeed) as a terminator, you can use a syntax similar to `--csv-line-terminator $'\n'`. | "\\r\\n" | | `--csv-output-dialect` | Indicates that the source data can be exported to a CSV file in a specific required format for the database. The option value can be `""`, `"snowflake"`, `"redshift"`, or `"bigquery"`. The default value is `""`, which means to encode and export the source data according to UTF-8. If you set the option to `"snowflake"` or `"redshift"`, the binary data type in the source data will be converted to hexadecimal, but the `0x` prefix will be removed. For example, `0x61` will be represented as `61`. If you set the option to `"bigquery"`, the binary data type will be encoded using base64. In some cases, the binary strings might contain garbled characters. | `""` | From eb7a733ada98c6b7854a7746a2c90cc5ce0696f3 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Thu, 27 Nov 2025 11:59:10 +0800 Subject: [PATCH 3/3] Update dumpling-overview.md --- dumpling-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dumpling-overview.md b/dumpling-overview.md index 2815d0396267f..d58c4c4ed6b52 100644 --- a/dumpling-overview.md +++ b/dumpling-overview.md @@ -406,7 +406,7 @@ SET GLOBAL tidb_gc_life_time = '10m'; | `--cert` | The address of the client certificate file for TLS connection | | `--key` | The address of the client private key file for TLS connection | | `--csv-delimiter` | Delimiter of character type variables in CSV files | '"' | -| `--csv-separator` | Separator for each value in CSV files. If your data contains commas, it is recommended to use an uncommon character as the separator. Invisible characters are also supported, for example: `--csv-separator $'\001'`. | ',' | +| `--csv-separator` | Separator for each value in CSV files. If your data contains commas, it is recommended to use a combination of uncommon characters as the separator. Invisible characters are also supported, for example: `--csv-separator $'\001'`. | ',' | | `--csv-null-value` | Representation of null values in CSV files | "\\N" | | `--csv-line-terminator` | The terminator at the end of a line for CSV files. When exporting data to a CSV file, you can specify the desired terminator with this option. This option supports "\\r\\n" and "\\n". The default value is "\\r\\n", which is consistent with the earlier versions. Because quotes in bash have different escaping rules, if you want to specify LF (linefeed) as a terminator, you can use a syntax similar to `--csv-line-terminator $'\n'`. | "\\r\\n" | | `--csv-output-dialect` | Indicates that the source data can be exported to a CSV file in a specific required format for the database. The option value can be `""`, `"snowflake"`, `"redshift"`, or `"bigquery"`. The default value is `""`, which means to encode and export the source data according to UTF-8. If you set the option to `"snowflake"` or `"redshift"`, the binary data type in the source data will be converted to hexadecimal, but the `0x` prefix will be removed. For example, `0x61` will be represented as `61`. If you set the option to `"bigquery"`, the binary data type will be encoded using base64. In some cases, the binary strings might contain garbled characters. | `""` |