Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

XDCR Advanced Filtering Reference

    +
    XDCR Advanced Filtering allows specified subsets of documents to be replicated from the source bucket.

    Configuring XDCR Filtering

    Full, Cluster, and XDCR Administrators can configure XDCR filtering. For a conceptual overview, see XDCR Advanced Filtering.

    XDCR Advanced Filtering can be performed on documents that contain a JSON object — with the keys and values surrounded by curly braces. It cannot be performed on documents that contain only a JSON array — with the elements surrounded only by square brackets.

    Regular and filtering expressions are applied, on the source cluster, to documents' keys, values, and metadata: documents that provide a match are replicated to the target; other documents are not replicated.

    Multiple expressions can be used by a single replication: the expressions should be ORed, as follows: filterExpression0|filterExpression1. For example, the expression airline|hotel would match both unitedairline and marriothotel.

    Filtering can be established when a replication is created, by means of Couchbase Web Console, CLI, or REST API. Once a replication is underway, its established filtering-expression can be modified; and the replication then either restarted or allowed to continue.

    Filtering does not impact conflict resolution, and can be used with either the revision-based or the timestamp-based conflict resolution policy. Filtering does not affect the ability to pause and resume replications. When multiple filtered replications are being established from the same source, expressions should typically be defined so as avoid the unnecessary re-replication of individual documents.

    Note that filtering may impact replication-performance; resulting in higher load, reduced throughput, and increased latency.

    A full account of XDCR Advanced Filtering expression-syntax is provided in XDCR Regular Expressions and XDCR Filtering Expressions. Note that expressions that attempt to compare values whose data types differ from one another must be handled either by data-type conversion or by collation comparison. These procedures, which are performed implicitly, are described in XDCR Data-Type Conversion.