gosonzhang opened a new issue, #6329: URL: https://github.com/apache/inlong/issues/6329
### Description At present, there are 2 modes of message processing of DataProxy: 1. The source side returns success or failure after receiving the message, and then sends the message through the channel and sink. Even if the channel and sink processing fails, the processing result will not be returned to the Client; 2. The source side does not return success or failure immediately after receiving the message, but waits until the sink sends it and then returns the success or failure result to the client, but this is done in an orderly synchronous sending mode; Based on the existing sending mode, we want to build a third type: 3. The source side does not return success or failure immediately after receiving the message, but waits until the sink sends it and then returns the success or failure result to the client. The sink returns the real sending success or failure message to the Client In order to distinguish the messages required by this type of service, we need the SDK to add "proxySend=true" to the properties of the message to indicate that this type of message requires DataProxy to process the message in the third way. ### InLong Component InLong DataProxy, InLong SDK ### 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]
