|On this page|
This node can be used to receive input data from a TOP Fetch
node in a different network. The TOP Fetch node in the original network will
write its attributes and input file list to JSON file. The path to that file is
available in this node via the
$PDG_FETCH_JSON_FILE environment variable.
Work Item Generation
Whether this node generates static or dynamic work items. You should generally leave this set to "Automatic" unless you know the node’s work items can be computed statically, or that they need to be generated dynamically.
This node always creates dynamic work items: it waits until the upstream work items are known, and generates new work items from the upstream work items.
This node always creates static work items: it creates the number of work items it thinks it needs based on the parameters (and any upstream static items) before the network runs.
If the input is static (a static processor, or a partitioner with only static inputs, or a mapper), this node generates static work items, otherwise it generates dynamic work items.
JSON Data File Path
The file path to the JSON data pack produced by the TOP Fetch node. The TOP Fetch Input will load the work item attributes and inputs from the file and create a copy of the work item in this node.
This example demonstrates how to use Top Fetch to fetch results from other top networks (using Top Fetch Input).
The following examples include this node.