PARTITION

Introduces logical segmentation within a single DDS domain.

What it controls

Which logical partition names a Publisher or Subscriber belongs to. Endpoints match only when their partition name sets overlap.

Key settings

Field	Default	Mutability
names	empty string	Can be changed at runtime

Compatibility role

Matching — partition names must overlap between Writer and Reader for a match. Affects discovery and late-join behavior when combined with durability or timing policies.

When this conflicts

Partition takes part in the following QoS Guard rules. Each links to a full explanation with an example and a fix.

Deadline monitoring interrupted when partitions change with DeadlineBreaks a guarantee Manual liveliness disrupted when partitions change with LivelinessBreaks a guarantee Partitions filter which retained samples a late joiner replays with DurabilityWastes resources Publisher and subscriber share no partition name with itselfWon't connect

Related policies

• DEADLINE
• LIVELINESS
• DURABILITY

Example

The PART QoS can be used to separate identical data types into multiple logical groups without the need to define additional topics or create new domains. For instance, delivery robots and inventory robots may share common topics such as "status" and "command" within the same domain, but still require distinct data flows. By setting the names=delivery for the delivery robots and names=inventory for the inventory robots, a central management system can subscribe only to the desired partition and selectively receive data from a specific group of robots.