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

Using --continue flag for dolt table import -u doesn't add any rows #2820

Closed
abmyii opened this issue Feb 16, 2022 · 6 comments
Closed

Using --continue flag for dolt table import -u doesn't add any rows #2820

abmyii opened this issue Feb 16, 2022 · 6 comments

Comments

@abmyii
Copy link
Contributor

abmyii commented Feb 16, 2022

This may be Windows-only. The version used was 0.37.0. The output info showed that the rows were added and Import successful, but the changes didn't persist.

@VinaiRachakonda
Copy link
Contributor

Can you provide a repro?

@abmyii
Copy link
Contributor Author

abmyii commented Feb 17, 2022

OK, this isn't Windows-only, but it seems to be specific to the setup of the us-housing-prices database (perhaps the constraints?). To test, run dolt table import -u sales test.csv on the master branch. Both rows are valid except that I have changed the hour from 00 to 99 for the first sale_date.
test.csv

This also occurs on dolt 0.36.2.

@VinaiRachakonda
Copy link
Contributor

  1. The attached schema in the csv file is very different from the table schema. Several of the column do not align with the schema, making it possible you are not actually updating a row to its new value.
  2. This issue helped me identify a bug in our import statistics calculator that needs to get fixed.

@abmyii
Copy link
Contributor Author

abmyii commented Feb 22, 2022

  • The attached schema in the csv file is very different from the table schema. Several of the column do not align with the schema, making it possible you are not actually updating a row to its new value.

I believe it is valid, as it worked once I removed the rows being skipped manually. I removed the additional columns and tried again, with result being the same, so I do think it is a bug in the importer.

test.csv

2. This issue helped me identify a bug in our import statistics calculator that needs to get fixed.

Great!

@VinaiRachakonda
Copy link
Contributor

Leaving as a note to myself. There is improper handling with --skip and violated check constraints.

@VinaiRachakonda
Copy link
Contributor

Merged in master

@timsehn timsehn closed this as completed Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants