cloud: clarify IMPORT INTO wildcard path matching

[alastori]

What is changed, added or deleted? (Required)

This PR corrects the TiDB Cloud guidance for wildcard paths in IMPORT INTO:

• Clarifies that wildcards can appear in multiple fixed-depth path components.
• Explains that a wildcard matches only within one /-separated component and does not provide arbitrary-depth recursive matching.
• Adds s3://<bucket-name>/dir/subdir*/*.csv as a fixed-depth S3 example.
• Preserves the existing TiDB Self-Managed v8.5 restriction through platform-specific content in the shared SQL reference.

The previous Cloud wording incorrectly limited wildcards to file names. TiDB now supports component-aware patterns such as dir/subdir*/*.csv, while still requiring each wildcard to remain within one path component.

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

• master (the latest development version)
• v8.5 (the branch used by the current TiDB Cloud documentation)
• v8.4
• v8.3
• v8.2
• v8.1
• v7.5
• v7.1
• v6.5

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

• Other reference links:
  • Support wildcard generation for CSV files stored in subdirectories tidb#67471
  • pkg/importsdk: fix wildcard generation for subdir csv files tidb#67472

Validation

• ./scripts/markdownlint sql-statements/sql-statement-import-into.md
• python3 scripts/file-format-lint.py sql-statements/sql-statement-import-into.md
• python3 scripts/check-manual-line-breaks.py sql-statements/sql-statement-import-into.md
• Verified the platform filters retain the new wording and example for TiDB Cloud while preserving the existing TiDB Self-Managed v8.5 text.
• Ran go test -tags=intest,deadlock ./pkg/importsdk -run 'Test(ValidatePattern|GenerateWildcardPath)$' -count=1 in the TiDB repository. The tests verify that the import SDK accepts and generates dir/subdir*/*.csv.
• Ran a direct IMPORT INTO smoke test against a local TiDB cluster and an S3-compatible MinIO endpoint using s3://import-smoke/fixture/dir/subdir*/*.csv. The job finished with four imported rows from two matching directories. Decoy objects in a different directory, one level deeper, with a non-CSV extension, and without the final file component were all excluded.

The direct SQL smoke test validates S3 path matching in the TiDB engine. It does not claim an end-to-end test against a live TiDB Cloud cluster or the Aurora/RDS Parquet workflow.

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
  • Clarified wildcard behavior for file locations in TiDB and TiDB Cloud.
  • Documented TiDB Cloud support for matching files in subdirectories at a fixed depth.
  • Added an example for selecting .csv files within subdirectories.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[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: b8a8a8f4-298e-4b01-b7bf-5249dffb9fa0

📥 Commits

Reviewing files that changed from the base of the PR and between b51acd5 and ba96fab.

📒 Files selected for processing (1)

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

---

📝 Walkthrough

Walkthrough

The fileLocation documentation now defines different wildcard behavior for TiDB and TiDB Cloud. It also includes a TiDB Cloud example for matching .csv files in subdirectories at a fixed depth.

Changes

fileLocation wildcard documentation

Layer / File(s)	Summary
Document platform-specific wildcard behavior sql-statements/sql-statement-import-into.md	The documentation limits TiDB wildcards to filenames. It allows TiDB Cloud wildcards across multiple path components without crossing / separators or matching arbitrary recursive depths. A fixed-depth .csv import example was added.

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

Merge Risk: ⚪ Minimal · up to ba96f

This localized documentation update clarifies wildcard path behavior and preserves platform-specific guidance; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 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 summarizes the main change: clarifying wildcard path matching for cloud IMPORT INTO documentation.
Description check	✅ Passed	The description explains the documentation changes, affected version, references, validation steps, and scope limitations; only optional template sections are omitted.

✨ 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]

[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 jackysp 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

[alastori]

@GMHDBJD PTAL

[alastori]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

[CLAassistant]

All committers have signed the CLA.