Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16281
Basically, the idea is to make a special build for Parquet 1.8.1 with the
needed fixes by ourselves.
Upgrading to newer version like Parquet 1.9.0 is risky. Parquet 1.9.0 was
just released this Oct. The bugs might not be exposed until more users/clients
start using it. This is also the same to our Spark community. I personally do
not suggest any enterprise customer use Spark 2.0.0, even if it resolved many
bugs in Spark 1.6+
To evaluate whether upgrading Parquet 1.9.0., the biggest effort is the
performance evaluation. We need to have our own standard performance workload
benchmarks (TPC-DS is not enough) to test whether the upgrade can introduce any
major performance degradation.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
