Github user kishorvpatil commented on the issue:
https://github.com/apache/spark/pull/12203
@vanzin, @jerryshao
Sorry for breaking this functionality. I have the patch available with more
unit tests added to ensure positive test case ensuring submission continues if
unique
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/12203
I think there was a version of Oozie that triggered that assert; so maybe
upgrading Oozie fixes the problem. It's also probably fine to remove that
assert since we haven't seen many people hit it,
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/12203
Maybe as you mentioned - skip adding to distributed cache and log warning -
is enough, throwing exception will fail the application and this is actually
not a fatal problem. I'm OK to change the
Github user RicoGit commented on the issue:
https://github.com/apache/spark/pull/12203
Thanks, i understand this is different problems. What will you advice me? I
think that this is not good solution: `require(localizedPath != null)` just
fails with exception message "requirements
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/12203
Can you make sure the problem you met is exactly the same as what this PR
solved? Since the exception stack you pasted in the StackOverFlow is different
from What I pasted here before. From you
Github user RicoGit commented on the issue:
https://github.com/apache/spark/pull/12203
Thanks for reply. I have [problem with running spark job with
oozie](http://stackoverflow.com/questions/38144022/oozie-spark-action-requirement-failed).
This patch solves my problem. I applied this
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/12203
@RicoGit This is a behavior change for jars uploading to distributed
cache, I'm not sure if it is suitable to back-port to branch 1.6. Also this
problem is not so severe in 1.6 since we do the
Github user RicoGit commented on the issue:
https://github.com/apache/spark/pull/12203
Hi guys, it is possible to apply this patch to version 1.6? What can I do
for this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
