Github user ksakellis commented on the pull request:
https://github.com/apache/spark/pull/3119#issuecomment-62447986
@vanzin regarding testing... yes, I did try what you recommended - I added
a note in the commit message. Snappy does some static initialization so if it
was unavailable when you first referenced the class, it will never be available
again. So i can create a unit test but then all the other snappy unit tests
fail. This is why i mentioned that I would need multiple classloaders to get
around this issue.
---
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]
