-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-15148][SQL] Upgrade Univocity library from 2.0.2 to 2.1.0 #12923
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
Conversation
|
LGTM pending Jenkins. |
|
So doing a quick grep shows that we are using the newly deprecated method If its really urgent to get this upgrade in quickly, lets make a follow up JIRA to move away from these deprecated functions for the next release. |
|
Thanks, @holdenk! It is not urgent. I can do this in this PR. |
|
Great! |
|
Test build #2975 has finished for PR 12923 at commit
|
|
Test build #57853 has finished for PR 12923 at commit
|
|
Test build #57861 has finished for PR 12923 at commit
|
|
LGTM, except that it needs a rebase now |
|
Test build #57875 has finished for PR 12923 at commit
|
|
Merging in master/branch-2.0. |
## What changes were proposed in this pull request? https://issues.apache.org/jira/browse/SPARK-15148 Mainly it improves the performance roughtly about 30%-40% according to the [release note](https://github.com/uniVocity/univocity-parsers/releases/tag/v2.1.0). For the details of the purpose is described in the JIRA. This PR upgrades Univocity library from 2.0.2 to 2.1.0. ## How was this patch tested? Existing tests should cover this. Author: hyukjinkwon <gurwls223@gmail.com> Closes #12923 from HyukjinKwon/SPARK-15148. (cherry picked from commit ac12b35) Signed-off-by: Reynold Xin <rxin@databricks.com>
What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-15148
Mainly it improves the performance roughtly about 30%-40% according to the release note. For the details of the purpose is described in the JIRA.
This PR upgrades Univocity library from 2.0.2 to 2.1.0.
How was this patch tested?
Existing tests should cover this.