Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/19113
We didn't accept parquet 1.9.0 because it has a known performance
regression, I think this one is fine, merging to master, thanks!
---
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19113
If we need 2.5.x for the fix, then we need 2.5.x. It's worth picking up an
update if it solves a real problem. And if we're going to update minor
versions, it's generally good practice to pick the la
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19113
Since the expected release of our next version Spark 2.3 is the end of this
year, we still can revert it back to 2.2.1 if we realize this release 2.5.4
introduces new bugs or performance regressi
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19113
This release of Univocity was just out a few days ago. To me, this sound
risky.
We normally do not upgrade it to the latest version. This is why we are
not using Parquet 1.9.0. Instead,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/19113
With 2.7G data, I ran a simple Java problem with 2.5.4 and 2.2.1 with
`CsvParser`, and simple e2e read tests. Elapsed time diff was roughly -1.7% ~
+1.2%. I think virtually no diff (or 0.5 impr
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19113
How about the other popular open source projects? Do you know whether which
projects are using Univocity 2.5?
---
If your project is set up for it, you can reply to this email and have your
repl
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19113
Any performance measure from 2.2 to 2.5?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19113
Merged build finished. Test PASSed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19113
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81368/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19113
**[Test build #81368 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81368/testReport)**
for PR 19113 at commit
[`fa7eb51`](https://github.com/apache/spark/commit/f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19113
**[Test build #81368 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81368/testReport)**
for PR 19113 at commit
[`fa7eb51`](https://github.com/apache/spark/commit/fa
11 matches
Mail list logo
