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
Current implementation: When the configured Topic cannot be found by groupId/streamId, the current implementation will select the default Topic on the Source side and forward it to the Sink side; after the Sink side receives the message, it will search for the Topic to be delivered according to the groupId/streamId again, if not If it exists, reject or discard the message
Which needs to be adjusted: when the configured topic cannot be found in the groupId/streamId, the Source side passes the default Topic backward, and the Sink side still needs to obtain the default Topic again when the configured Topic cannot be found in the groupId/streamId. There are repeated operations; adjust them to be performed only on the Sink side, which facilitates the unification of Topic selection logic.
Description
Current implementation: When the configured Topic cannot be found by groupId/streamId, the current implementation will select the default Topic on the Source side and forward it to the Sink side; after the Sink side receives the message, it will search for the Topic to be delivered according to the groupId/streamId again, if not If it exists, reject or discard the message
Which needs to be adjusted: when the configured topic cannot be found in the groupId/streamId, the Source side passes the default Topic backward, and the Sink side still needs to obtain the default Topic again when the configured Topic cannot be found in the groupId/streamId. There are repeated operations; adjust them to be performed only on the Sink side, which facilitates the unification of Topic selection logic.
InLong Component
InLong DataProxy
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: