Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9134#discussion_r42111793
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -655,6 +655,15 @@ object SparkSubmit {
// scalastyle:on println
}
System.exit(CLASS_NOT_FOUND_EXIT_STATUS)
+ case e: NoClassDefFoundError =>
--- End diff --
I think this OK. (PS the exception isn't "unreadable" -- just
"uninformative"). `NoClassDefFoundError` is lower-level problem; classes were
compiled in the presence of some other classes that aren't available at
runtime. It's "worse" than `ClassNotFoundException`. It probably makes sense,
but is this really a problem of building *without* Hive support? I would kind
of think it's the opposite: you built with Hive and then it's not available at
runtime?
---
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
