-
Notifications
You must be signed in to change notification settings - Fork 847
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
Don't try to infer nullability in CSV reader #2860
Conversation
FYI. I'm going to fix these clippy errors ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me -- thanks @Dandandan
I think it would help to put an additional comment in the docstring of infer_reader_schema
saying that the inferred schema will always have
nullable fields as it may be done on a sample of the data.
Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
Benchmark runs are scheduled for baseline = 65d5576 and contender = 1397fb4. 1397fb4 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
🎉 |
…s#2860) Signed-off-by: Fedomn <fedomn.ma@gmail.com>
Which issue does this PR close?
Closes #2859
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?
Yes, inference always returns null datatypes for inference