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.

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

Make LOAD DATA statements support commit and rollback like normal DMLs in a transaction #49078

Closed
ekexium opened this issue Dec 1, 2023 · 0 comments
Assignees
Labels
type/feature-request Categorizes issue or PR as related to a new feature.

Comments

@ekexium
Copy link
Member

ekexium commented Dec 1, 2023

Feature Request

Is your feature request related to a problem? Please describe:

Consider this,

begin;
load data ...
load data ...
commit; or rollback;

The LOAD DATA statements should not take effect until the surrounding transaction commits or rolls back. But in current TiDB(v7.5), a LOAD DATA statement commits its current transaction, then starts loading data, then commits its content after the statement finishes.
Besides, a LOAD DATA statement can be non-atomic, i.e. it can import part of the data and commits anyway. We would like the statement to be atomic.

Describe the feature you'd like:

Make LOAD DATA statements in transactions behave like normal DMLs.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

@ekexium ekexium added the type/feature-request Categorizes issue or PR as related to a new feature. label Dec 1, 2023
@ekexium ekexium self-assigned this Dec 1, 2023
ti-chi-bot bot pushed a commit that referenced this issue Dec 18, 2023
@ekexium ekexium closed this as completed Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature-request Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant