Multiple replications to the same destination cluster and bucket are not allowed, even if they have different filter expressions
Description
In the "Configure XDCR filtering" section, there is the following statement:
"The filtering expression becomes a part of the key for replication. Therefore, administrators can create multiple replications to the same destination cluster and bucket as long as the filtering expression is different."
This statement came from the original PRD. The requirement and design was changed later, though. In the actual xdcr implementation, the filtering expression is not a part of the key for replication, and multiple replications to the same destination cluster and bucket are not allowed, even if they have different filtering expressions.
The rationale for changing the design is that if there is a need to replicate to the same destination cluster and bucket with different filtering expressions, it can be achieved by creating a single replication with the filter expression being multiple expressions "or"ed together, e.g., filterExpression0|filterExpression1.
The following sample expression would match both "unitedairline" and "marriothotel":
airline|hotel
We should
remove this statement from the doc.
provide suggestions like the above.
Environment
None
Release Notes Description
None
Activity
Show:
Shilpa Lele May 8, 2017 at 4:07 PM
Edited
Updated 5.0, 4.6, 4.5, and 4.1 versions.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
In the "Configure XDCR filtering" section, there is the following statement:
"The filtering expression becomes a part of the key for replication. Therefore, administrators can create multiple replications to the same destination cluster and bucket as long as the filtering expression is different."
This statement came from the original PRD. The requirement and design was changed later, though. In the actual xdcr implementation, the filtering expression is not a part of the key for replication, and multiple replications to the same destination cluster and bucket are not allowed, even if they have different filtering expressions.
The rationale for changing the design is that if there is a need to replicate to the same destination cluster and bucket with different filtering expressions, it can be achieved by creating a single replication with the filter expression being multiple expressions "or"ed together, e.g., filterExpression0|filterExpression1.
The following sample expression would match both "unitedairline" and "marriothotel":
airline|hotel
We should
remove this statement from the doc.
provide suggestions like the above.