|On this page|
$HH/help/files/pdg_examples/top_partitioners example shows how you can use common partitioner features like targeted partitioning, controls for merging attributes, and splitting by attribute.
Determines how the work item range is specified.
Custom range based on a ratio of upstream items to partition count and an offset in the left/right directions.
Creates a fixed number of partitions no matter how many upstream work items there are. Upstream items are distributed as evenly as possible among the partitions. If the items don’t divide evenly, the first few partitions will have an extra work item.
Creates partitions of a fixed size when possible. If the upstream items don’t divide evenly, only the last partition will have the wrong size. It will contain whatever items are left after dividing the upstream items into groups of the desired fixed size.
Creates exactly two partitions. The first one contains the first work item from each of the input nodes, and the second partition contains the last work item from each of the input nodes. Other upstream items are not partitioned.
Create exactly three partitions. Behaves the same as the First/Last range type, except the middle work items from each input node are also put into a partition.
These parameters configure the behavior of the partitioner when the Custom Range type is selected. The range is determined by two main properties: the ratio of upstream work items to partitions, and an offset in the left and right direction.
For example, with Upstream Range set to 2 and Partition Range set to 1, one partition will be created for every two upstream work items.
Along with the Partition Range parameter, determines the ratio between upstream work items and partitions
Determines the number of partitions to create, along with the Upstream Range parameter.
The number of additional items proceeding the selected items that should also be included in the partitions.
The number of additional items that follow the selected items that should also be included in the partitions.
The number of partitions that will be created.
The number of upstream items that will be added to each partition.
These parameters control how attributes from input work items are merged onto the partitions produced by the node.
Defines the number of attribute merge operations to perform on the partitioner node. The operations are used to merge attributes from work items in the partition onto the partition itself. Operations are performed in descending order. Attributes are merged using the first operation with a pattern that matches the attribute.
Specifies the operation to perform to merge incoming attributes onto the partition. Each operation only applies only to the subset of attributes matched using the corresponding To Attributes parameter.
The following operations are available:
Matching attributes are ignored and will not appear on the partition.
The value of each matching attribute on the first work item in the partition is kept, and values on subsequent work items are ignored
The value of each matching attribute on the last work item in the partition is kept.
The unique values for each matching attribute are merged into an array. Duplicate values are discarded.
Append to Array
The values for each matching attribute are appended to an array for that attribute. All attribute values from all work items are kept.
The minimum value for each matching attribute is kept.
The maximum value for each matching attribute is kept.
The sum of the values in each matching attribute is stored on the partition.
The average value of each matching attribute is stored on the partition.
The most common value in each matching attribute is kept.
The middle value in each matching attribute is kept.
Specifies which attributes the corresponding Apply Operation parameter should apply to. This field can use the Attribute Pattern Syntax to specify multiple attributes.
These are advanced parameters that provide finer control over the behavior of the partitioner.
Determines when the partitioning step is performed on the input work items.
Input Items are Generated
Upstream work items are partitioned once all of them have been generated
Input Items Are Cooked
Upsteam work items are partitioned once all of them are cooked. This may be required when the partitioning scheme is based on the results of the work items' execution.
This makes this partitioner behave like a Wait for All node except that it may create multiple partitions.A
Determines which node or nodes(s) should target. Work items in the target nodes are partitioned as soon as they're generated even if the target nodes are not a direct input to this node. The descendants of the target work items are added to the partitions when they become available.
Direct Input Nodes
The partitioner uses work items from its direct input nodes. This is the default behavior
Upstream Static Nodes
The partitioner will skip over dynamic input nodes and partition work items from the nearest upstream static nodes.
Custom Target Node
The partitioner will use the node specified using the Custom Target Node parameter.
Custom Target Node
Specifies the target TOP node for the partition when Partition Targets is set to Custom Target Node. The partition scheme is applied to the work items in the target TOP node instead of this node’s input work items. The target TOP node must be in the same graph and above this node.
Split by Attribute
When on, the node splits input work items by the specified attribute(s) before partitioning them. The partitioning logic is evaluated on the list of work items for each distinct attribute value. Work items with different attribute values are always put into different partitions. Multiple attribute names can be specified as a space-separated list.
Determines how the node handles work items that are missing the split attribute.
This parameter is only available when Split by Attribute is on.
Ignore Work Item
Work items that are missing the split attribute are not put into any of the partitions.
Partitioner Defines Behavior
The partitioner node determines what happens to work items that are missing the split attribute. Typically a partitioner node that exposes this option will rename this menu entry to describe the actual operation it performs.
Add Work Item to All Partitions
Work items that are missing the split attribute are put into all of the partitions.
Use Default Value
Work items that are missing the split attribute will use the value set in the Default Value parameter.
When Missing Attribute is set to Use Default Value, this parameter specifies the value to use for the split attribute for work items that don’t have the attribute.
Allow Partial Matches
When Split by Attribute is set to a list of attribute names, this parameter determines how work items with only some of the attributes should be processed. If partial matches are enabled then work items will be added to split groups based on the attributes that do exist. Otherwise, work items with only a subset of the attributes will be excluded from the partitioning step.
Sort Contents By
Determines the order that work items are sorted in when accessing the partitions on this node. This also affects the sort order of output files on the partition.
No sorting is applied. The work items in the partition are handled in no particular order.
Work Item Index
Work items in the partition are sorted based on their index.
Input Node Order
Work items in the partition are sorted based on the order of input nodes wired into this node. If two work items are from the same input, they are then sorted by index.
Work items in the partition are sorted based on the attribute specified in the Sort Attribute field parameter.
Determines whether the work items in this node’s partitions are sorted in ascending or descending order.
Specifies the name of the attribute to sort by.
This parameter is only available when Sort Contents By is set to Attribute.