Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18200
I am not against fixing this within Spark for now. That would be a
workaround anyway and I guess we want to remove out when upgrading Univocity.
In favour of
https://github.com/uniVocity/univocity-parsers/commit/08b67c3017c765b75f4b72dfeae743427f0f0ca6,
this was fixed but looks the bug is not only about single length string.
If the fix is simple, I could work around for now but I am not sure if it
is that simple. I guess using existing functionalities should be safe. Also,
there is another (not for now) related issue fixed in
`https://github.com/uniVocity/univocity-parsers/issues/143`.
I will ask to the author if it is safe or not again when I am about to open
a PR. I guess we will have some time to check this after upgrading this (in the
early state of a release, Spark 2.3.0, assuming 2.2.0 release is soon) and it
should be good to find/report other bugs in Univocity if there are.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
