ningyanhui opened a new issue, #13728:
URL: https://github.com/apache/dolphinscheduler/issues/13728

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   
spark-submit提交py-files时正确操作应将执行的.py文件放在--py-files后,但是dolphinscheduler生成的执行语句放在了前面。
   正确如:
   park-submit --master yarn --deploy-mode cluster --driver-cores 1 
--driver-memory 512M --num-executors 2 --executor-cores 2 --executor-memory 2G 
--name cut_chat_message_with_jieba --queue default  --jars 
"obs://juexiao-bigdata/pyspark/user_feedback/huaweicloud-dws-jdbc-8.1.1.300-200.jar"
  --py-files 
"obs://juexiao-bigdata/pyspark/user_feedback/jx-batch-pyspark.zip,obs://juexiao-bigdata/pyspark/user_feedback/jieba.zip"
 pyspark/user_feedback_cut_word_with_jieba.py   -d  '2023-03-09'
   dolphinscheduler生成语句是:
   park-submit --master yarn --deploy-mode cluster --driver-cores 1 
--driver-memory 512M --num-executors 2 --executor-cores 2 --executor-memory 2G 
--name cut_chat_message_with_jieba --queue default 
pyspark/user_feedback_cut_word_with_jieba.py --jars 
"obs://juexiao-bigdata/pyspark/user_feedback/huaweicloud-dws-jdbc-8.1.1.300-200.jar"
  --py-files 
"obs://juexiao-bigdata/pyspark/user_feedback/jx-batch-pyspark.zip,obs://juexiao-bigdata/pyspark/user_feedback/jieba.zip"
    -d  '2023-03-09'
   
   ### What you expected to happen
   
   spark-submit提交py-files时正确操作应将执行的.py文件放在--py-files后
   
   ### How to reproduce
   
   spark-submit提交py-files时正确操作应将执行的.py文件放在--py-files后
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.1.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to