qy-liuhuo commented on code in PR #11119:
URL: https://github.com/apache/inlong/pull/11119#discussion_r1766114399
##########
inlong-sdk/dataproxy-sdk/src/main/java/org/apache/inlong/sdk/dataproxy/DefaultMessageSender.java:
##########
@@ -191,6 +195,10 @@ public String getSDKVersion() {
return ConfigConstants.PROXY_SDK_VERSION;
}
+ public void enableDataTruncation(boolean enableDataTruncation) {
+ this.enableDataTruncation = enableDataTruncation;
Review Comment:
So should we replace the truncation policy with the reject policy？
It seems that it is not easy to tell whether the data can be truncated at
the sending end.
I think if the receiver can't handle the truncated content, it should also
return an error message to the sender
--
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
