Document IMPORT INTO restriction for TTL-enabled tables

[D3Hunter]

What is changed, added or deleted? (Required)

Document that IMPORT INTO does not support importing data into a table with TTL enabled.

The restrictions list already covered temporary and cached tables but omitted TTL-enabled tables. As described in pingcap/tidb#70426, an asynchronous TTL job can delete rows while an import is running, which can cause the final checksum verification to fail. This update closes that documentation gap so users can avoid running IMPORT INTO against an unsupported target table.

Validation: ./scripts/markdownlint sql-statements/sql-statement-import-into.md and git diff --check.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):
  • Issue: IMPORT INTO can fail with checksum mismatch when target table has TTL enabled tidb#70426
  • PR: importinto: forbid importing into TTL-enabled tables tidb#70427

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

Summary by CodeRabbit

• Documentation
  • Updated IMPORT INTO restrictions to clarify that tables with TTL enabled cannot be used as import targets, alongside temporary and cached tables.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign oreoxmt for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0bd4b838-b46d-43a7-85d9-78a99ea1f104

📥 Commits

Reviewing files that changed from the base of the PR and between 97bbec4 and a2970a4.

📒 Files selected for processing (1)

• sql-statements/sql-statement-import-into.md

---

📝 Walkthrough

Walkthrough

The IMPORT INTO documentation now prohibits imports into tables with TTL enabled. Existing restrictions for temporary and cached tables remain.

Changes

IMPORT INTO restrictions

Layer / File(s)	Summary
Document TTL restriction sql-statements/sql-statement-import-into.md	The restriction now includes tables with TTL enabled alongside temporary and cached tables.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related issues

• pingcap/tidb#70426 — Both changes reject IMPORT INTO operations for tables with TTL enabled.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers the change, rationale, validation, links, and selected versions, but it omits v8.5 listed in the PR objectives.	Update the version checklist to include v8.5 if this documentation change applies to that release.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely describes the documented restriction for IMPORT INTO and TTL-enabled tables.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ti-chi-bot]

@joechenrh: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-08-12 07:43:16.880575678 +0000 UTC m=+3205182.916670735: ☑️ agreed by lilin90.