[INLONG-10463][SDK] Optimization of ultra-long field processing in InlongSDK (Temp) #11213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #10463
Last Pr: #11119
Motivation
In #11119 We discussed how to get the
max message size
configuration. Everyone had different ideas. Finally, we decided to temporarily configure it locally in theDataProxy SDK
.If the message is longer than the
ConfigConstants.MAX_MESSAGE_LENGTH
, it will directly returnBODY_EXCEED_MAX_LEN
errorModifications
ConfigConstants.MAX_MESSAGE_LENGTH
constant in theConfigConstants
fileDataBodyUtil
to get the msg size of body or bodyListDefaultMessageSender
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:)
Documentation