Github user eggsby commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108526035
@vanzin - if people are depending on parquet transitively through spark
then they simply need to make their dependency explicit, but yes - sparks
public facing signatures that expose **parquet types will need to be updated
downstream in user code in order to compile**.
This is inevitable unless spark intends to stay on an incubating release
candidate version of parquet until some major version change like 2.0 - and is
willing to accommodate the parquet bugs that come along with that.
Please be advised of the associated risk, but I still believe upgrading
parquet is a good idea.
---
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
