Describe the question
In the DolphinScheduler 1.3.6 version:
Api Server is run as a springBoot application , with embedded jetty server (9.4. x )
Api Server depend on dolphinscheduler-common jars , both depends on hadoop-common、 hadoop-client jar‘s
The hadoop-common, hadoop-client has not excusion jetty third jars , such as org.mortbay.jetty.jetty , org.mortbay.jetty.jetty.util.
When start up Api server process , It has load jars , which in the lib directory:
has jetty-6.1.26 , jetty 9.x (from spring-boot-starter-jetty.)
may causes startup failure, for example throw jasper.runtimeError. throw java.lang.NoSuchFieldError: IS_SECURITY_EANBLED
What are the current deficiencies and the benefits of improvement
A clear and concise description of the current deficiencies and the benefits of this improvement.
Therefore, it is suggested to exclued the jetty dependency in Hadoop command and hadoop client jar's
Which version of DolphinScheduler:
-[1.3.6]
Describe alternatives you've considered
The api Server is a springBoot project as a web backend project. The hadoop job exectued by work server .
So I suggest to remove the low jettey dependency in api-server.
For better global communication, please give priority to using English description, thx!
Please review https://dolphinscheduler.apache.org/en-us/community/development/issue.html when describe an issue.
Describe the question In the DolphinScheduler 1.3.6 version:
What are the current deficiencies and the benefits of improvement
Which version of DolphinScheduler: -[1.3.6]
Describe alternatives you've considered The api Server is a springBoot project as a web backend project. The hadoop job exectued by work server . So I suggest to remove the low jettey dependency in api-server.