kuansix opened a new pull request, #6255: URL: https://github.com/apache/inlong/pull/6255
Prepare a Pull Request (Change the title refer to the following example) Title: [INLONG-6212][Sort] Support multiple sink for DorisLoadNode (The following XYZ should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number) Fixes https://github.com/apache/inlong/issues/6212 Motivation Support multiple sink for DorisLoadNode.In this scenario, we agree that the upstream data stream is binary data in a certain format such as 'canal-json' or 'debezium', and the main processing steps as follows: Deserialize the binary data by the format specified with 'sink.multiple.format' Dynamic extract the database and table from it used with 'sink.multiple.database-pattern' and 'sink.multiple.table-pattern' Convert the deserialized data to the json data that is used for Doris StreamLoad Use StreamLoad load data to Doris used with the database and table that is extracted earlier. Modifications 1.Add DorisDynamicSchemaOutputFormat 2.Update DorisStreamLoad,DorisDynamicTableSink,DorisDynamicTableFactory 3.Update DorisLoadNode 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]
