Github user elmer-garduno commented on the pull request:
https://github.com/apache/spark/pull/3874#issuecomment-68607699
The problem seems to be fixed when using `spark-submit` instead of
`spark-class`, that seems to set the appropriate precedence on the classpaths,
so no need for any special flags or changes here.
Thanks
---
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]
