Skip to content

Commit 445d5c8

Browse files
authored
dumpling: clarify description about --csv-separator (#22098)
1 parent 05b4188 commit 445d5c8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

dumpling-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -406,7 +406,7 @@ SET GLOBAL tidb_gc_life_time = '10m';
406406
| `--cert` | The address of the client certificate file for TLS connection |
407407
| `--key` | The address of the client private key file for TLS connection |
408408
| `--csv-delimiter` | Delimiter of character type variables in CSV files | '"' |
409-
| `--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| ',' | ',' |
409+
| `--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'`. | ',' |
410410
| `--csv-null-value` | Representation of null values in CSV files | "\\N" |
411411
| `--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" |
412412
| `--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. | `""` |

0 commit comments

Comments
 (0)