Note: this is an abstract component, that cannot be instantiated.
The Distribution Partition defines a partition for a distribution algorithm.
A distribution algorithm splits a subtree into several partitions. Each partition has an identifier which is unique throughout all the topology of servers. This means that when two distributions are configured on two servers and they are referring to the same data partition, they must refer to that partition using the same partition identifier. This is a requirement because indexes can be replicated between servers. Each partition has its own parameters. The partition parameters depend on the type of the partition. For example, partition parameters for a numeric distribution consist of a lower bound and upper bound. Each partition is mapped to a workflow element. The workflow element mapped to the partition can be of any type (load balancer, final workflow element) but from the partition perspective the workflow element is a data container.
The following Distribution Partitions are available in the server :
These Distribution Partitions inherit from the properties described below.
The following components have a direct AGGREGATION relation FROM Distribution Partitions :
The following components have a direct COMPOSITION relation TO Distribution Partitions :
This page describes the Distribution Partition:
A description of each property follows.
| Basic Properties: | Advanced Properties: |
|---|---|
| ↓ partition-id | None |
| ↓ workflow-element |
| Description | Identifies the partition. The partition identifier is unique for a given data partition. The identifier is an integer. |
| Default Value | None |
| Allowed Values | An integer value. Lower value is 0. |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | Yes |
| Description | The workflow element which contains the partition. |
| Default Value | None |
| Allowed Values | The DN of any Workflow Element. |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | Yes |
Each configuration property can be mapped to a specific LDAP attribute under the "cn=config" entry. The mappings that follow are provided for information only. In general, you should avoid changing the server configuration by manipulating the LDAP attributes directly.
| Base DN | cn=partitions |
| objectclass name | ds-cfg-distribution-partition |
| objectclass superior | top |
| Property | LDAP attribute |
| partition-id | ds-cfg-distribution-partition-id |
| workflow-element | ds-cfg-workflow-element |