You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by "emptyOVO (via GitHub)" <gi...@apache.org> on 2024/11/17 11:04:26 UTC

[I] [Feature][Manager] Support schedule engine configuration [inlong]

emptyOVO opened a new issue, #11504:
URL: https://github.com/apache/inlong/issues/11504

   ### Description
   
   According pr: #11484  and pr: #11486 
   1. At present, manager and dashboard only support the selection of third-party engines, but they cannot be configured directly, requiring manual modification of the properties file and then recompilation, which makes it inefficient and not easy to use from the user's perspective. If we need to change the relevant configuration in the configuration file every time, we will not be able to handle multiple tasks that require multiple engines to schedule
   
   ![67b51eac-dacc-4dc0-a762-a57183b7c018](https://github.com/user-attachments/assets/f85c2c62-aabb-49b2-b767-f5a3240af11e)
   we can see there is no place for configure engine details
   personally think related configuration can be configured in dashboard and call in service may be a good idea
   
   2. The present configuration of DolphinScheduler is incorrect, DS engine also be able to select schedule interval and unit, which can be handle in `DolphinScheduleUtils` in pr: #11468 
   ![86c58fc1-5c3b-4f83-8b06-6f7071a6b8b9](https://github.com/user-attachments/assets/cf2a0f55-80b4-4756-a46c-df1a3a1e5d4c)
   
   
   3. Some configuration may needs to be config in dashboard
   * for Airflow: according pr: #11479 ,there may need configs below
   ```properties
   # Airflow API URL
   airflow.baseUrl=
   airflow.connection.id=
   airflow.username=
   airflow.password=
   # Please confirm if it is a loopback address
   inlong.manager.host=
   # DAG Deleter and Creator ID
   airflow.cleaner.id=
   airflow.creator.id=
   ```
   
   * for DolphinScheduler: according pr: #11468 ,there may need configs below
   ```properties
   # DolphinScheduler related config
   inlong.schedule.dolphinscheduler.url=
   inlong.schedule.dolphinscheduler.token=
   ```
   
   ### Use case
   
   _No response_
   
   ### 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: dev-unsubscribe@inlong.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug][Dashboard] DolphinScheduler should support conventional config [inlong]

Posted by "emptyOVO (via GitHub)" <gi...@apache.org>.
emptyOVO closed issue #11504: [Bug][Dashboard] DolphinScheduler should support conventional config
URL: https://github.com/apache/inlong/issues/11504


-- 
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: dev-unsubscribe@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug][Dashboard] DolphinScheduler should support conventional config [inlong]

Posted by "emptyOVO (via GitHub)" <gi...@apache.org>.
emptyOVO closed issue #11504: [Bug][Dashboard] DolphinScheduler should support conventional config
URL: https://github.com/apache/inlong/issues/11504


-- 
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: dev-unsubscribe@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org