- Key Features
- Horizontal Scalability
- MySQL Compatible Syntax
- Replicate from and to MySQL
- Distributed Transactions with Strong Consistency
- Cloud Native Architecture
- Minimize ETL with HTAP
- Fault Tolerance & Recovery with Raft
- Automatic Rebalancing
- Deployment and Orchestration with Ansible, Kubernetes, Docker
- JSON Support
- Spark Integration
- Read Historical Data Without Restoring from Backup
- Fast Import and Restore of Data
- Hybrid of Column and Row Storage
- SQL Plan Management
- Open Source
- Online Schema Changes
- Key Features
- Get Started
- From Binary Tarball
- Orchestrated Deployment
- Geographic Redundancy
- SQL Language Structure
- Data Types
- Numeric Types
- Date and Time Types
- String Types
- Functions and Operators
- Function and Operator Reference
- Type Conversion in Expression Evaluation
- Control Flow Functions
- String Functions
- Numeric Functions and Operators
- Date and Time Functions
- Bit Functions and Operators
- Cast Functions and Operators
- Encryption and Compression Functions
- Information Functions
- JSON Functions
- Aggregate (GROUP BY) Functions
- Window Functions
- Miscellaneous Functions
- Precision Math
- List of Expressions for Pushdown
- SQL Statements
ADMIN CANCEL DDL
ADMIN CHECKSUM TABLE
ADMIN CHECK [TABLE|INDEX]
ADMIN SHOW DDL [JOBS|QUERIES]
CREATE TABLE LIKE
SET DEFAULT ROLE
SET [NAMES|CHARACTER SET]
SET [GLOBAL|SESSION] <variable>
SHOW ANALYZE STATUS
SHOW CHARACTER SET
SHOW [FULL] COLUMNS FROM
SHOW CREATE TABLE
SHOW CREATE USER
SHOW [FULL] FIELDS FROM
SHOW INDEXES [FROM|IN]
SHOW INDEX [FROM|IN]
SHOW KEYS [FROM|IN]
SHOW [FULL] PROCESSSLIST
SHOW [FULL] TABLES
SHOW TABLE REGIONS
SHOW TABLE STATUS
SHOW [GLOBAL|SESSION] VARIABLES
- System Databases
- Garbage Collection (GC)
- Understanding the Query Execution Plan
- The Blocklist of Optimization Rules and Expression Pushdown
- Introduction to Statistics
- TopN and Limit Push Down
- Optimizer Hints
- Follower Read
- Check the TiDB Cluster Status Using SQL Statements
- Execution Plan Binding
- Statement Summary Table
- Tune TiKV
- Operating System Tuning
- Column Pruning
- Key Monitoring Metrics
- Best Practices
- TiDB Binlog
- Binlog Consumer Client
- TiDB Binlog Relay Log
- Bidirectional Replication Between TiDB Clusters
- TiDB Lightning
- All Releases
TiDB Lightning supports reading CSV (comma-separated values) data source, as well as other delimited format such as TSV (tab-separated values).
A CSV file representing a whole table must be named as
db_name.table_name.csv. This will be
restored as a table
table_name inside the database
If a table spans multiple CSV files, they should be named like
The file extension must be
*.csv, even if the content is not separated by commas.
CSV files are schema-less. To import them into TiDB, a table schema must be provided. This could be done either by:
- Providing a file named
CREATE TABLEDDL statement
- Creating the empty tables directly in TiDB in the first place, and then setting
[mydumper] no-schema = truein
The CSV format can be configured in
tidb-lightning.toml under the
Most settings have a corresponding option in the MySQL
LOAD DATA statement.
[mydumper.csv] # Separator between fields, should be an ASCII character. separator = ',' # Quoting delimiter, can either be an ASCII character or empty string. delimiter = '"' # Whether the CSV files contain a header. # If `header` is true, the first line will be skipped. header = true # Whether the CSV contains any NULL value. # If `not-null` is true, all columns from CSV cannot be NULL. not-null = false # When `not-null` is false (i.e. CSV can contain NULL), # fields equal to this value will be treated as NULL. null = '\N' # Whether to interpret backslash escapes inside fields. backslash-escape = true # If a line ends with a separator, remove it. trim-last-separator = false
Defines the field separator.
Must be a single ASCII character.
Corresponds to the
FIELDS TERMINATED BYoption in the LOAD DATA statement.
Defines the delimiter used for quoting.
delimiteris empty, all fields are unquoted.
'"'quote fields with double-quote, same as RFC 4180
Corresponds to the
FIELDS ENCLOSED BYoption in the
- Whether all CSV files contain a header row.
headeris true, the first row will be used as the column names. If
headeris false, the first row is not special and treated as an ordinary data row.
not-nullsetting controls whether all fields are non-nullable.
not-nullis false, the string specified by
nullwill be transformed to the SQL NULL instead of a concrete value.
Quoting will not affect whether a field is null.
For example, with the CSV file: ```csv A,B,C \N,"\N", ``` In the default settings (`not-null = false; null = '\N'`), the columns `A` and `B` are both
converted to NULL after importing to TiDB. The column
Cis simply the empty string
''but not NULL.
Whether to interpret backslash escapes inside fields.
backslash-escapeis true, the following sequences are recognized and transformed:
| Sequence | Converted to | |----------|--------------------------| | `\0` | Null character (U+0000) | | `\b` | Backspace (U+0008) | | `\n` | Line feed (U+000A) | | `\r` | Carriage return (U+000D) | | `\t` | Tab (U+0009) | | `\Z` | Windows EOF (U+001A) | In all other cases (for example, `\"`) the backslash is simply stripped, leaving the next character (`"`) in the field. The character left has no special roles (for example, delimiters) and is just an ordinary character.
Quoting will not affect whether backslash escapes are interpreted.
Corresponds to the
FIELDS ESCAPED BY '\'option in the
Treats the field
separatoras a terminator, and removes all trailing separators.
For example, with the CSV file:
trim-last-separator = false, this is interpreted as a row of 5 fields
('A', '', 'B', '', '').
trim-last-separator = true, this is interpreted as a row of 3 fields
('A', '', 'B').
TiDB Lightning does not support every option supported by the
LOAD DATA statement. Some examples:
- The line terminator must only be CR (
\r), LF (
\n) or CRLF (
LINES TERMINATED BYis not customizable.
- There cannot be line prefixes (
LINES STARTING BY).
- The header cannot be simply skipped (
IGNORE n LINES), it must be valid column names if present.
- Delimiters and separators can only be a single ASCII character.
The default setting is already tuned for CSV following RFC 4180.
[mydumper.csv] separator = ',' delimiter = '"' header = true not-null = false null = '\N' backslash-escape = true trim-last-separator = false
ID,Region,Count 1,"East",32 2,"South",\N 3,"West",10 4,"North",39
[mydumper.csv] separator = "\t" delimiter = '' header = true not-null = false null = 'NULL' backslash-escape = false trim-last-separator = false
ID Region Count 1 East 32 2 South NULL 3 West 10 4 North 39
[mydumper.csv] separator = '|' delimiter = '' header = false not-null = true backslash-escape = false trim-last-separator = true
1|East|32| 2|South|0| 3|West|10| 4|North|39|