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

Jump to bottom

importccl: IMPORT MYSQLDUMP does not handle ON DELETE CASCADE #28553

Closed
dt opened this issue Aug 14, 2018 · 1 comment
Closed

importccl: IMPORT MYSQLDUMP does not handle ON DELETE CASCADE #28553

dt opened this issue Aug 14, 2018 · 1 comment
Assignees
@dt
Labels
A-disaster-recovery C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
Milestone
2.1

Comments

@dt
Copy link
Member

dt commented Aug 14, 2018

If the mysql schema's FKs specify an action, IMPORT will error trying to read them. Worse, as a parse error, we don't have anything useful to tell the user, so it is just the "error (maybe something unsupported?)"
@dt dt self-assigned this Aug 14, 2018
@dt dt mentioned this issue Aug 14, 2018
Closed
@dt dt added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. A-disaster-recovery labels Aug 14, 2018
@dt dt added this to Triage in Bulk IO via automation Aug 14, 2018
@dt dt added this to the 2.1 milestone Aug 14, 2018
@dt dt moved this from Triage to Milestone Aug 20th in Bulk IO Aug 14, 2018
@dt dt moved this from Milestone Aug 20th to Aug 20th Done in Bulk IO Aug 15, 2018
@dt
Copy link
Member Author

dt commented Aug 16, 2018

#28648

@dt dt closed this as completed Aug 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dt dt

Labels
A-disaster-recovery C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
Projects
None yet
Milestone
2.1
Development

No branches or pull requests
1 participant
@dt