Migrate Data from CSV Files to TiDB

This document describes how to migrate data from CSV files to TiDB.

TiDB Lightning can read data from CSV files and other delimiter formats, such as tab-separated values (TSV). For other flat file data sources, you can also refer to this document and migrate data to TiDB.

Prerequisites

Step 1. Prepare the CSV files

Put all the CSV files in the same directory. If you need TiDB Lightning to recognize all CSV files, the file names should meet the following requirements:

  • If a CSV file contains the data for an entire table, name the file ${db_name}.${table_name}.csv.
  • If the data of one table is separated into multiple CSV files, append a numeric suffix to these CSV files. For example, ${db_name}.${table_name}.003.csv. The numeric suffixes can be inconsecutive but must be in ascending order. You also need to add extra zeros before the number to ensure all the suffixes are in the same length.

Step 2. Create the target table schema

Because CSV files do not contain schema information, before importing data from CSV files into TiDB, you need to create the target table schema. You can create the target table schema by either of the following two methods:

  • Method 1: create the target table schema using TiDB Lightning.

    Create SQL files that contain the required DDL statements:

    • Add CREATE DATABASE statements in the ${db_name}-schema-create.sql files.
    • Add CREATE TABLE statements in the ${db_name}.${table_name}-schema.sql files.
  • Method 2: create the target table schema manually.

Step 3. Create the configuration file

Create a tidb-lightning.toml file with the following content:

  1. [lightning]
  2. # Log
  3. level = "info"
  4. file = "tidb-lightning.log"
  6. [tikv-importer]
  7. # "local": Default backend. The local backend is recommended to import large volumes of data (1 TiB or more). During the import, the target TiDB cluster cannot provide any service.
  8. # "tidb": The "tidb" backend is recommended to import data less than 1 TiB. During the import, the target TiDB cluster can provide service normally.
  9. # For more information on import mode, refer to <https://docs.pingcap.com/tidb/stable/tidb-lightning-overview#tidb-lightning-architecture>
  10. backend = "local"
  11. # Set the temporary storage directory for the sorted Key-Value files. The directory must be empty, and the storage space must be greater than the size of the dataset to be imported. For better import performance, it is recommended to use a directory different from `data-source-dir` and use flash storage, which can use I/O exclusively.
  12. sorted-kv-dir = "/mnt/ssd/sorted-kv-dir"
  14. [mydumper]
  15. # Directory of the data source.
  16. data-source-dir = "${data-path}" # A local path or S3 path. For example, 's3://my-bucket/sql-backup'.
  18. # Defines CSV format.
  19. [mydumper.csv]
  20. # Field separator of the CSV file. Must not be empty. If the source file contains fields that are not string or numeric, such as binary, blob, or bit, it is recommended not to usesimple delimiters such as ",", and use an uncommon character combination like "|+|" instead.
  21. separator = ','
  22. # Delimiter. Can be zero or multiple characters.
  23. delimiter = '"'
  24. # Configures whether the CSV file has a table header.
  25. # If this item is set to true, TiDB Lightning uses the first line of the CSV file to parse the corresponding relationship of fields.
  26. header = true
  27. # Configures whether the CSV file contains NULL.
  28. # If this item is set to true, any column of the CSV file cannot be parsed as NULL.
  29. not-null = false
  30. # If `not-null` is set to false (CSV contains NULL),
  31. # The following value is parsed as NULL.
  32. null = '\N'
  33. # Whether to treat the backslash ('\') in the string as an escape character.
  34. backslash-escape = true
  35. # Whether to trim the last separator at the end of each line.
  36. trim-last-separator = false
  38. [tidb]
  39. # The target cluster.
  40. host = ${host}            # e.g.: 172.16.32.1
  41. port = ${port}            # e.g.: 4000
  42. user = "${user_name}"     # e.g.: "root"
  43. password = "${password}"  # e.g.: "rootroot"
  44. status-port = ${status-port} # During the import, TiDB Lightning needs to obtain the table schema information from the TiDB status port. e.g.: 10080
  45. pd-addr = "${ip}:${port}" # The address of the PD cluster, e.g.: 172.16.31.3:2379. TiDB Lightning obtains some information from PD. When backend = "local", you must specify status-port and pd-addr correctly. Otherwise, the import will be abnormal.

For more information on the configuration file, refer to TiDB Lightning Configuration.

Step 4. Tune the import performance (optional)

When you import data from CSV files with a uniform size of about 256 MiB, TiDB Lightning works in the best performance. However, if you import data from a single large CSV file, TiDB Lightning can only use one thread to process the import by default, which might slow down the import speed.

To speed up the import, you can split a large CSV file into smaller ones. For a CSV file in a common format, before TiDB Lightning reads the entire file, it is hard to quickly locate the beginning and ending positions of each line. Therefore, TiDB Lightning does not automatically split CSV files by default. But if your CSV files to be imported meet certain format requirements, you can enable the strict-format mode. In this mode, TiDB Lightning automatically splits a single large CSV file into multiple files, each in about 256 MiB, and processes them in parallel.

Migrate from CSV Files - 图1

Note

If a CSV file is not in a strict format but the strict-format mode is set to true by mistake, a field that spans multiple lines will be split into two fields. This causes the parsing to fail, and TiDB Lightning might import the corrupted data without reporting any error.

In a strict-format CSV file, each field only takes up one line. It must meet the following requirements:

  • The delimiter is empty.
  • Each field does not contain CR (\r) or LF (\n).

If your CSV file meets the above requirements, you can speed up the import by enabling the strict-format mode as follows:

  1. [mydumper]
  2. strict-format = true

Step 5. Import the data

To start the import, run tidb-lightning. If you launch the program in the command line, the process might exit unexpectedly after receiving a SIGHUP signal. In this case, it is recommended to run the program using a nohup or screen tool. For example:

  1. nohup tiup tidb-lightning -config tidb-lightning.toml > nohup.out 2>&1 &

After the import starts, you can check the progress of the import by either of the following methods:

After TiDB Lightning completes the import, it exits automatically. Check whether tidb-lightning.log contains the whole procedure completed in the last lines. If yes, the import is successful. If no, the import encounters an error. Address the error as instructed in the error message.

Migrate from CSV Files - 图2

Note

Whether the import is successful or not, the last line of the log shows tidb lightning exit. It means that TiDB Lightning exits normally, but does not necessarily mean that the import is successful.

If the import fails, refer to TiDB Lightning FAQ for troubleshooting.

Other file formats

If your data source is in other formats, to migrate data from your data source, you must end the file name with .csv and make corresponding changes in the [mydumper.csv] section of the tidb-lightning.toml configuration file. Here are example changes for common formats:

TSV:

  1. # Format example
  2. # ID    Region    Count
  3. # 1     East      32
  4. # 2     South     NULL
  5. # 3     West      10
  6. # 4     North     39
  8. # Format configuration
  9. [mydumper.csv]
  10. separator = "\t"
  11. delimiter = ''
  12. header = true
  13. not-null = false
  14. null = 'NULL'
  15. backslash-escape = false
  16. trim-last-separator = false

TPC-H DBGEN:

  1. # Format example
  2. # 1|East|32|
  3. # 2|South|0|
  4. # 3|West|10|
  5. # 4|North|39|
  7. # Format configuration
  8. [mydumper.csv]
  9. separator = '|'
  10. delimiter = ''
  11. header = false
  12. not-null = true
  13. backslash-escape = false
  14. trim-last-separator = true

What’s next