Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108518882
I did (and still do) have concerns, because upgrading a dependency changes
the classpath user applications see. And now, suddenly, all the old `parquet.*`
packages are going to disappear, which may affect existing user applications.
I don't know enough about Spark's use of parquet to know whether any
parquet types end up leaking through the API somehow, though. If that case
doesn't exist, then this change would be a little more palatable. But,
generally, upgrading dependencies like this is a little bit sketchy from a
user's perspective.
---
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]
