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

Optional Supression of Date Parse Warning? #54

Open
sdmcallister opened this issue Apr 9, 2020 · 1 comment
Open

Optional Supression of Date Parse Warning? #54

sdmcallister opened this issue Apr 9, 2020 · 1 comment

Comments

@sdmcallister
Copy link

Does this seem like a sensible option to add?

I have a date column where there are tens of thousands of 0 values. I like the warning intially, but very quickly it fills up the terminal.

To avoid the warnings I could (should I?) try to handle this prior to passing the data to the schema parser using a regex? Maybe just use an intCol and create a new column that is parsed? Any suggestions are appreciated.

@bluenote10
Copy link
Owner

Yes this has been marked as a todo for a while, but I never had a good idea how aggregate these errors in a way that doesn't impact complexity too much. Probably we would have to use Option[Time] in general then?

In practice you probably can work-around the problem by keeping the field as a string initially, and then apply a mapper with your own string-to-date conversion with fallbacks.

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

2 participants