ignore_origin overrides the default handling of transactions from different origins, and allows them to be partitioned as if they all came from the same origin.
All partitioning rules, except ignore_origin, allow transactions from different origins to be applied in parallel, regardless of other specified partitioning rules.
alter connection dataserver.db set dsi_partitioning_rule to "name"
In this case, transactions with different origins are applied in parallel, whether or not they have the same name.
The name partitioning rule only affects transactions from the same origin. Thus, transactions with the same origin and name are applied serially, and transactions with the same origin and different names are applied in parallel.
If ignore_origin is listed first in the alter connection statement, Replication Server partitions transactions with the same or different origins according to the second or succeeding rules in the statement. For example:
alter connection dataserver.db set dsi_partitioning_rule to "ignore_origin, name"
In this case, all transactions with the same name are applied serially and all transactions with different names are applied in parallel. The origin of the transaction is irrelevant.
If ignore_origin is listed in the second or a succeeding position in the alter connection statement, Replication Server ignores it.