Github user mallman commented on the issue:
https://github.com/apache/spark/pull/16281
I'd love to see frequent, conservative patch releases. From my experience,
parquet bugs cause significant trouble for downstream consumers. For example,
we encountered a data corruption bug writing parquet format V2 that made a good
deal of that data unreadable. (I can't recall the issue number, but it was
reported and fixed.)
As another example, we recently upgraded some of our Spark clusters to use
parquet-mr 1.9.0, because PARQUET-363 introduced a bug into one of our Spark
2.x patches. When we switched to 1.9, we found
https://issues.apache.org/jira/browse/PARQUET-783, which breaks things in a
different way. We needed a fix, so we forked 1.9 internally.
FWIW, we haven't found any other issues using parquet-mr 1.9.0 with Spark
2.1.
---
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
