[fix] Fix issue where DisableReplication flag does not work #1100
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.
Motivation
When producing a message, we can specify the
DisableReplication
option, and if set to true, the message is expected not to be replicated to remote clusters. However, this option currently does not work, and even if set to true, messages will be replicated to remote clusters.The following part is the cause of this issue.
pulsar-client-go/pulsar/producer_partition.go
Lines 554 to 559 in ac9c1a6
If
DisableReplication
is true,ReplicationClusters
is set to__local__
. However, the metadata that is actually sent to the broker has already been constructed immediately before that. Therefore, there is no point in changing the value ofReplicationClusters
here. The order of these two must be reversed.Modifications
Construct the metadata after changing
ReplicationClusters
to__local__
.Verifying this change