chovy-3012 opened a new issue, #18695: URL: https://github.com/apache/dolphinscheduler/issues/18695
## Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ## Description When configuring a Spark task, three high-frequency `spark-submit` options can only be passed through a single free-text "others" box: | Option | Why users need it | |---|---| | `--py-files` | Required by nearly every PySpark job to distribute dependent `.py`/`.zip`/`.egg` files to executors | | `--archives` | Frequently used to distribute `.tar`/`.zip`/`.tgz` archives (e.g. config bundles, native libs) to executors | | `--principal` / `--keytab` | Mandatory for Spark jobs on Kerberized Hadoop clusters — every secured production environment needs this | Users must hand-type the exact CLI syntax into a generic text box, with no resource picker, no path validation, and no UI guidance. This is error-prone, especially for non-CLI-savvy users. ## Why these matter - `--py-files` — used in virtually every PySpark job; the most frequent option for Python-type Spark tasks. - `--archives` — a go-to option whenever jobs need config bundles or native libs on executors; common in production. - `--principal` / `--keytab` — required on every secured Hadoop cluster; no Kerberized environment can run Spark without it. These are not edge-case flags — they appear in the majority of production Spark submissions. Dedicated fields with resource-center integration would eliminate the most common configuration errors. ## Related issues None ## Are you willing to submit a PR? - [X] 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]
