0 / 0
Configuring runtime properties for the Hierarchical Data stage

Configuring runtime properties for the Hierarchical Data stage

To modify how the Hierarchical Data stage runs in the job, configure these properties.

Heap Size (MB)
Enter the maximum heap size, in MB, for the Java™ Virtual Machine. This property corresponds to the -Xmx command line option. Specify at least 256 MB. Consider specifying a larger heap size if the assembly includes a large schema and large documents.
Stack Size (KB)
Enter the size of the stack, in KB, for the Java Virtual Machine. This property corresponds to the -Xss command line option.
Other Options
Enter additional command line arguments to the Java Virtual Machine. For example, to set a system property, enter DSystemProperty=Value.
Use Scratch Disk
Yes (default) specifies that at runtime, data might be written to disk if processing does not fit into main memory. If set to No, the job might fail at runtime if processing does not fit into main memory. Performance is faster if you do not use a scratch disk; however, you risk not having enough memory for the job.
Limit Output Rows
Enter Yes for Limit output rows, and then enter a value for Maximum output rows. Limiting output rows is useful when you are debugging a job and do not want to wait for the results of the entire job.
Maximum Output Rows
Enter Yes for Limit output rows, and then enter a value for Maximum output rows. Output rows are calculated cumulatively across all output links. The Hierarchical Data stage stops processing after generating the maximum number of output rows.
Enable logging
Enter Yes to enable logging and set the log level to Warning. By default, logging is not enabled. Enabling logging affects performance.
Log level
You can set the log level to one of the following values. The values are listed by the amount of messages that are logged, from least to most. Each level includes all of the messages that are logged by the previous level. Choosing a high level of logging affects performance.
FATAL
Errors that cause a process to fail are logged.
ERROR
Errors that might not cause a process to fail are logged.
WARN
Messages about conditions that might cause errors or other issues are logged.
INFO
General informational messages are logged.
DEBUG
Specific informational messages that might be useful for troubleshooting are logged.
TRACE
Very specific informational messages that might be useful for troubleshooting are logged.
Generative AI search and answer
These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more