You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When dealing with pr[1], I found that DataProxy separately defines the property Key value for message interaction between SDK and DataProxy. This information should be placed in InLong-Common, so that when dealing with cross-module content, the same Key It can avoid repeated definitions, or the problem that the key value is defined incorrectly and the corresponding value cannot be obtained.
Change all message attribute Keys generated by SDK and used by DataProxy or other modules to be obtained from org.apache.inlong.common.msg.AttributeConstants;
The message attribute Key generated by DataProxy and returned to the receiver through the message attribute is placed in the org.apache.inlong.common.msg.AttributeConstants file, and the generation direction is marked;
Change the file name of org.apache.inlong.dataproxy.consts.AttributeConstants to org.apache.inlong.dataproxy.consts.AttrConstants to avoid confusing references with the same name as org.apache.inlong.common.msg.AttributeConstants
healchow
changed the title
[Improve][DataProxy] Use the defined message attribute Key value in InLong-Common
[Improve][DataProxy] Use the defined message attribute key value in InLong-Common
Nov 3, 2022
Description
When dealing with pr[1], I found that DataProxy separately defines the property Key value for message interaction between SDK and DataProxy. This information should be placed in InLong-Common, so that when dealing with cross-module content, the same Key It can avoid repeated definitions, or the problem that the key value is defined incorrectly and the corresponding value cannot be obtained.
InLong Component
InLong DataProxy
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: