Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16281
Yes, but we face bugs in third-party components all the time and work
around them or get them fixed. There is an unmentioned downside here too: not
getting bug fixes and improvements that don't (yet) affect Spark. Running a
fork risks incompatibility at the data format level, where it matters most to
interop. I think this really can't be taken lightly -- better to find ways to
increase integration testing or influence on Parquet or whatever to get things
fixed faster where they bite Spark.
---
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
