Zkplo opened a new issue, #11533:
URL: https://github.com/apache/inlong/issues/11533
### Description
`org.apache.inlong.manager.service.schedule.ScheduleOperatorImpl`
````java
private ScheduleEngineClient getScheduleEngineClient(String scheduleEngine) {
if (scheduleEngineClient == null) {
scheduleEngineClient =
scheduleClientFactory.getInstance(scheduleEngine);
}
return scheduleEngineClient;
}
````
At present, the single instance mode is adopted. When a user selects any
scheduling engine from the front-end to issue offline tasks, the subsequent
selection of the scheduling engine will follow the first one, and there is a
possibility of scheduling engine selection failure.In order to support multiple
scheduling engines, it is necessary to modify the code logic here.
### InLong Component
InLong Manager
### Are you willing to submit 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]
