Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5546#issuecomment-94728926
Yeah I doubt it will affect any user-facing code since those class names
aren't massive. It might affect compatibility between two builds of Spark,
since these functions get referenced in closures. It might be surprising that
Spark built at the same tag on encrypted vs unencrypted file systems isn't
compatible. That said I don't have any concrete evidence of this being a
problem in practice. I think this is fine as a 'canary'? Nit: maven -> Maven in
the doc change. LGTM.
---
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]
