The Lexico Distribution Partition defines a partition for a lexicographic distribution algorithm.
A lexicographic distribution algorithm is based on a partitioning key (named the distribution attribute) and a set of lexicographic partitions. A lexicographic partition is defined by a lower bound and an upper bound. When a distribution attribute value is inside the range of the lexicographic partition then the target entry is a member of the partition. For example, if the distribution attribute is 'sn' and if one lexicographic partition bound is ["A"-"E"], then the entry containing "sn=BOB" is a member of that partition, while the entry containing "cn=PAT" is not.
The lower bound of the partition. The lower bound of the partition is a string. This bound can be as small as a single character or it can be larger. Both values "A" and "BEGIN" are valid bound values. Use the keyword 'unlimited' if the lower bound is not limited.
Default Value
None
Allowed Values
A String
Multi-valued
No
Required
Yes
Admin Action Required
None
Advanced Property
No
Read-only
Yes
partition-id
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
upper-bound
Description
The upper bound of the partition. The upper bound of the partition is a string. This bound can be as small as a single character or it can be larger. Both values "Z" and "END" are valid bound values. Use the keyword 'unlimited' if the upper bound is not limited.
Default Value
None
Allowed Values
A String
Multi-valued
No
Required
Yes
Admin Action Required
None
Advanced Property
No
Read-only
Yes
workflow-element
Description
The workflow element which contains the partition.
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.