liaorui opened a new pull request, #6746: URL: https://github.com/apache/inlong/pull/6746
### Prepare a Pull Request *(Change the title refer to the following example)* - Title Example: [INLONG-XYZ][Component] Title of the pull request *(The following *XYZ* should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number)* - Fixes #6745 ### Motivation *Explain here the context, and why you're making that change. What is the problem you're trying to solve?* Inspired by doris-cdc-inlong, starrocks-cdc-inlong can also support transferring all tables in one database on time. StarRocks FE api has changed, been different from Doris FE api. If you use doris-cdc-inlong to handle StarRocks tables writing, it will give a error: http://x.x.x.x:xxxx/api/backends?is_alive=true failed. java.io.IOException: Failed to get response from Doris. That is why we need a sarrocks-cdc-inlong connector. This PR provides StarRocks load node management is InLong Manager. ### Modifications *Describe the modifications you've done.* 1. SinkType has new STARROCKS type. 2. manager-pojo has new StarRocksSink, StarRocksSinkDTO and StarRocksSinkRequest classes. 3. LoadNodeUtils has new createLoadNode method for creating StarRocksLoadNode object. 4. manager-service has new StarRocksSinkOperator class. ### Verifying this change *(Please pick either of the following options)* - [ ] This change is a trivial rework/code cleanup without any test coverage. - [ ] This change is already covered by existing tests, such as: *(please describe tests)* - [ ] This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end deployment with large payloads (10MB)* - *Extended integration test for recovery after broker failure* ### Documentation - Does this pull request introduce a new feature? (yes / no) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) - If a feature is not applicable for documentation, explain why? - If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation -- 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]
