qy-liuhuo opened a new pull request, #11119:
URL: https://github.com/apache/inlong/pull/11119
<!-- Prepare a Pull Request
Change the title of pull request refer to the following example:
[INLONG-XYZ][Component] Title of the pull request
-->
<!-- Specify the issue this pull request going to fix.
The following *XYZ* should be replaced by the actual [GitHub
Issue](https://github.com/apache/inlong/issues) number)-->
Fixes #10463
### Motivation
Due to dataproxy limitations, a CONNECTION_BREAK error will occur when
sending too much data through the SDK. So this PR solves the following problems：
1. Support automatic ultra-long data truncation in SDK
2. User-configurable automatic truncation
3. Provide the default value of the allowed data length
### Modifications
1. Added a `MAX_MESSAGE_LENGTH` constant in
`inlong-sdk/dataproxy-sdk/src/main/java/org/apache/inlong/sdk/dataproxy/ConfigConstants.java`.
2. Provided a `DataTruncationUtil` to implement data truncation.
3. Added the `enableDataTruncation` property to `DefaultMessageSender.java`
to determine whether to enable the automatic truncation function. And added a
configuration function for users to call.
4. Add data truncation logic to all `sendMessage` and `asyncSendMessage`
interfaces.
Now you can open the automatic truncation function by
`sender.enableDataTruncation(true);`
And you can also change the default `MAX_MESSAGE_LENGTH` constant at
`ConfigConstants.java` file
### Verifying this change
*(Please pick either of the following options)*
- [x] 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: commits-unsubscr...@inlong.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
