This repository has been archived by the owner on Jan 9, 2020. It is now read-only.
Check the existence of the user jars/files before creating the driver pod/service #85
Comments
lins05
added a commit
to lins05/spark
that referenced
this issue
Feb 4, 2017
ash211
pushed a commit
that referenced
this issue
Feb 8, 2017
) * Check for user jars/files existence before creating the driver pod. Close #85 * CR
ash211
pushed a commit
to palantir/spark
that referenced
this issue
Feb 16, 2017
) * Check for user jars/files existence before creating the driver pod. Close apache-spark-on-k8s#85 * CR
ash211
pushed a commit
that referenced
this issue
Mar 8, 2017
) * Check for user jars/files existence before creating the driver pod. Close #85 * CR
foxish
pushed a commit
that referenced
this issue
Jul 24, 2017
) * Check for user jars/files existence before creating the driver pod. Close #85 * CR
puneetloya
pushed a commit
to puneetloya/spark
that referenced
this issue
Mar 11, 2019
…pache-spark-on-k8s#86) * Check for user jars/files existence before creating the driver pod. Close apache-spark-on-k8s#85 * CR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If the user jars/files doesn't exist (or there is a typo), it's better to fail before creating the driver pod/service.
The text was updated successfully, but these errors were encountered: