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

DBaaS : v5.2.0 lightning import parquet file in pending #27605

Closed
apollodafoni opened this issue Aug 26, 2021 · 1 comment · Fixed by #27607
Closed

DBaaS : v5.2.0 lightning import parquet file in pending #27605

apollodafoni opened this issue Aug 26, 2021 · 1 comment · Fixed by #27607
Assignees
Labels
affects-5.2 This bug affects 5.2.x versions. component/lightning This issue is related to Lightning of TiDB. severity/critical type/bug The issue is confirmed as a bug.

Comments

@apollodafoni
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

import parquet file from S3
180GB
stop importing duiring precheck
middle_img_v2_ac367f67-595e-4a90-98e5-dd6b0c74d2cg

2. What did you expect to see? (Required)

import success

3. What did you see instead (Required)

no import progress

4. What is your TiDB version? (Required)

v5.2.0

@apollodafoni apollodafoni added type/bug The issue is confirmed as a bug. severity/critical component/lightning This issue is related to Lightning of TiDB. labels Aug 26, 2021
@jebter jebter added the affects-5.2 This bug affects 5.2.x versions. label Aug 31, 2021
@glorv glorv closed this as completed Oct 29, 2021
@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-5.2 This bug affects 5.2.x versions. component/lightning This issue is related to Lightning of TiDB. severity/critical type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants