Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16281
Thank you for review, @rxin .
Forking may give more controllability, but it goes invisible (in terms of
documents) soon.
According to the recent mail on Spark dev list, only committers seem to
know the latest repository location of Spark Hive fork.
I also want to contribute some on that, but it's difficult for me to find
how to do.
Every Apache projects (including Apache Spark) have some bugs at every
release.
I don't think there is no bug on Parquet 1.9.0. But, Parquet community
exists to improve that, doesn't it?
BTW, @rxin and @srowen . To reduce the risk,
- Do you want to add more Spark-side test case here?
- Or, do you prefer to skip 1.9.0 and go 1.10 directly?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
