Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/12268
@rxin I see. Actually, I added a benchmark for this change in the JIRA.
So.. would this be okay if I do as below:
1. Get rid of `StringIteratorReader`
2. Refactoring (maybe with a follow-up for the tests for.. `JacksonParser`,
`JacksonGenerator`, `UnivocityParser` and `UnivocityGenerator`)
3. Use Record API from univocity and compare the performance (with a proper
benchmark)
4. Maybe other fixes addressing @hvanhovell's comments (maybe with a
benchmark)
If it makes sense, I would appreciate that If I can create a umbrella for
those four as sub-tasts and be assigned to them.
---
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]
