Set policy

The XDR namespace sub-stanza can pinpoint specific sets to either ship or not ship to the remote datacenter.

• All sets are shipped unless you specifically exclude some of them.
• There is no intersection between sets and bins; that is, you cannot selectively ship or exclude bins from a specific set.
• The set based filtering is done prior to adding into the XDR transaction queue (transaction-queue-limit). On the other hand, XDR filters are applied as part of the function that reads the record, when elements are picked up from the XDR transaction queue and handed off to the service thread. Set and XDR filters are also re-evaluated when processing potential items from the retry queue.

What	Associated parameters	Default	Behavior of parameter combinations
Set	ship-only-specified-sets ship-set setName ignore-set setName	ship-only-specified-sets false ship-set has no default. ignore-set has no default.	To send only a specific set, specify ship-only-specified-sets true and ship-set setName. You can have multiple ship-set entries. Alternatively, to exclude a particular set, rely on the default ship-only-specified-sets false and use ignore-set setName. You can have multiple ignore-set entries.

Example shipping specific sets

In this example, for namespace someNameSpaceName, onlysetName1 and setName2 are shipped. The parameter ship-only-specified-sets is true, which is the opposite of its default false.

xdr {
    dc dataCenter1 {
        node-address-port someIpAdress1 somePort1
        namespace someNameSpaceName {
           ship-only-specified-sets true
           ship-set setName1
           ship-set setName2
        }
    }
}

Example excluding specific sets

In this example, for namespace someNameSpaceName, all sets are shipped except setName1 and setName2.

xdr {
    dc dataCenter1 {
        node-address-port someIpAdress1 somePort1
        namespace someNameSpaceName {
           ignore-set setName1
           ignore-set setName2
        }
    }
}