DebugFlow 2.7.1

Bundle
org.apache.nifi | nifi-standard-nar
Description
The DebugFlow processor aids testing and debugging the FlowFile framework by allowing various responses to be explicitly triggered in response to the receipt of a FlowFile or a timer event without a FlowFile if using timer or cron based scheduling. It can force responses needed to exercise or test various failure modes that can occur when a processor runs. It can also generate large numbers of component state entries for testing state management limits.
Tags
FlowFile, debug, flow, processor, state, test, utility
Input Requirement
Supports Sensitive Dynamic Properties
false
  • Additional Details for DebugFlow 2.7.1

    DebugFlow

    When triggered, the processor loops through the appropriate response list. A response is produced the configured number of times for each pass through its response list, as long as the processor is running.

    Triggered by a FlowFile, the processor can produce the following responses.

    1. transfer FlowFile to success relationship.
    2. transfer FlowFile to failure relationship.
    3. rollback the FlowFile without penalty.
    4. rollback the FlowFile and yield the context.
    5. rollback the FlowFile with penalty.
    6. throw an exception.

    Triggered without a FlowFile, the processor can produce the following responses.

    1. do nothing and return.
    2. throw an exception.
    3. yield the context.
Properties
State Management
Scopes Description
CLUSTER, LOCAL When 'Generate State Entries' is set to a positive integer, the processor will generate that many state entries with random values. This is useful for testing component state storage and display limits. State entries are stored with keys like 'debug_state_key_00000' with randomly generated values.
Relationships
Name Description
failure FlowFiles that failed to process.
success FlowFiles processed successfully.