Custom metadata collisions

Content Platform Tenant Management Help

Version
9.7.x
File Size
4269 KB
Audience
anonymous
Part Number
MK-95HCPH002-19

A custom metadata collision occurs when these events occur in the order shown:

  1. One of these changes occurs:
    • Custom metadata is added to a given object on each of two systems in a replication topology, but the added custom metadata is different on the two systems.

      The addition of custom metadata to an object on only one of the systems does not result in a custom metadata collision. Instead, the new custom metadata is replicated from that system to the other system without conflict.

    • The custom metadata for a given object is replaced on each of two systems in a replication topology, but the replacement custom metadata is different on the two systems.
    • The custom metadata for a given object is replaced on one system in a replication topology, and the same custom metadata is removed on another system in the topology.
  2. The change made on one of the systems is replicated to the other system.

Custom metadata is treated as a single unit. If a collision occurs when a custom metadata change for a given object is replicated from one system (system A) in a replication topology to another system (system B) in the topology:

  • If the last change on system A is more recent than the last change on system B, HCP applies the change from system A to the custom metadata on system B
  • If the last change on system B is more recent than the last change on system A, HCP does not change the custom metadata on system B

For example, suppose a given object starts out with the same custom metadata on system A and system B. The table below shows a sequence of events in which the custom metadata for the object is changed and the change is then replicated.

  1. On system B, a client replaces the custom metadata for the object with new custom metadata.
  2. On system A, a client replaces the custom metadata for the object with different custom metadata from the custom metadata used on system B.
  3. The change on system A is replicated to system B. The resulting custom metadata for the object on system B is the new custom metadata from system A.