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: mysqloutfile requires \n at EOF #25876

Closed
maddyblue opened this issue May 23, 2018 · 1 comment
Closed

importccl: mysqloutfile requires \n at EOF #25876

maddyblue opened this issue May 23, 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.

Comments

@maddyblue
Copy link
Contributor

A file containing no \n at EOF has its line ignored.
@maddyblue maddyblue added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-disaster-recovery labels May 23, 2018
@maddyblue maddyblue added this to Triage in Bulk IO via automation May 23, 2018
@maddyblue
Copy link
Contributor Author

Maybe we don't care because mysqldump doesn't produce this. But I found it during testing and it was confusing. If a user tried to hand write their own file or had some post processing it could get messed up.

@vivekmenezes vivekmenezes moved this from Triage to Milestone June 25 - Todo in Bulk IO May 29, 2018
@craig craig bot closed this as completed in a38fdb5 Jun 1, 2018
@maddyblue maddyblue moved this from Milestone June 25 - Todo to MIlestone June 25th Done in Bulk IO Jun 12, 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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dt @maddyblue