Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve usage of IMPORT FROM SELECT #19777

Merged
merged 3 commits into from
Dec 24, 2024
Merged

Improve usage of IMPORT FROM SELECT #19777

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ee985f2
Update sql-statement-import-into.md
hfxsd Dec 24, 2024
99bea44
Update wording
lilin90 Dec 24, 2024
cf85ecc
Update sql-statements/sql-statement-import-into.md
hfxsd Dec 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions sql-statements/sql-statement-import-into.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ The `IMPORT INTO` statement lets you import data to TiDB via the [Physical Impor
- `IMPORT INTO ... FROM SELECT` does not support the task management statements such as `SHOW IMPORT JOB(s)` and `CANCEL IMPORT JOB <job-id>`.
- The [temporary directory](https://docs.pingcap.com/tidb/stable/tidb-configuration-file#temp-dir-new-in-v630) of TiDB requires sufficient space to store the entire query result of the `SELECT` statement (configuring the `DISK_QUOTA` option is not supported currently).
- Importing historical data using [`tidb_snapshot`](/read-historical-data.md) is not supported.
- Due to the complexity of the `SELECT` clause syntax, the `WITH` parameter in `IMPORT INTO` might conflict with it, causing parsing errors, such as `GROUP BY ... [WITH ROLLUP]`. It is recommended to create a view for complex `SELECT` statements and then use `IMPORT INTO ... FROM SELECT * FROM view_name` for importing. Alternatively, you can clarify the scope of the `SELECT` clause with parentheses, such as `IMPORT INTO ... FROM (SELECT ...) WITH ...`.
lilin90 marked this conversation as resolved.
Show resolved Hide resolved

## Prerequisites for import

Expand Down
Loading