Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4873#issuecomment-77863414
Sorry to bug @pwendell again but I think you may also be familiar with this
script. I went to the extreme and removed the check for Hive jars entirely.
Datanucleus goes on the classpath if it exists, full stop. This also resolves
the JAR issue. But is there a reason that's a bad idea? Like, if I didn't build
with Hive, but Datanucleus is lying around, does that cause a problem?
---
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
