Github user pankajarora12 commented on the pull request:
https://github.com/apache/spark/pull/930#issuecomment-45066860
1. What if the user application legitimately has a flag called --arg? Won't
this cause it to break?
So there are already reserved keywords like --
--name
--master ....
which user apps cannot use because spark considers them as special words.
So asking the user to use different name rather than using --arg would be a
good idea .Also in case spark starts using --arg for some special meaning user
applications using --arg as application parameters will break.
2. Also (just wondering) - why do you think users would be setting --arg...
just from previous submissions scripts in Spark?
I have scheduling framework written for firing jobs to spark. After
upgrading to spark 1.0.0 my application was broken and it took me quite a lot
time to find out why it was not taking parameters. So any one upgrading from
previous version to 1.0.0 will face the same problem and they have to debug to
find out whats failing. So an error message would be very useful.
---
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.
---
