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

   ### 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
   
   I’d like to fix some unreasonable settings in DolphinScheduler UI for Spark 
task parameters.
   
   ### Problem 1: Required/optional mismatch between validation and placeholder
   Current behavior: mainClass is required by form validation, but the 
placeholder text indicates it is optional. And master is optional (should be 
optional), but the placeholder and validation currently treat it as required.
   <img width="2432" height="1618" alt="Image" 
src="https://github.com/user-attachments/assets/2071f37e-0470-44f7-9447-ce5067a241ae";
 />
   
   ### Problem 2: master parameter should be available for all Spark task types
   Current behavior: only Scala and Java Spark tasks can configure master 
separately in the UI. SQL and Python task types cannot.
   
   <img width="2338" height="1480" alt="Image" 
src="https://github.com/user-attachments/assets/2fbb9977-13d7-4bb6-9568-6984f8b89807";
 />
   
   ### Expected: 
   1. Placeholder/help text should match validation.
   2. Master should be configurable for Scala / Java / SQL / Python Spark task 
types 
   
   <img width="2536" height="1442" alt="Image" 
src="https://github.com/user-attachments/assets/c0bee2f4-cc83-4b31-90ff-79e63976ad74";
 />
   
   <img width="1950" height="1174" alt="Image" 
src="https://github.com/user-attachments/assets/5067cedc-dff2-4c5e-896a-01dfd4e6026e";
 />
   
   ### 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]

Reply via email to