Skip to content

TRIGGER REPROCESS

Description

The TRIGGER REPROCESS processor is designed to initiate the reprocessing of data within a specified schema. This processor is particularly useful for scenarios where data needs to be reprocessed due to changes in the data schema, updates in the data source, or corrections in the processing logic.

Config Location

To configure the TRIGGER REPROCESS processor, you need to define it within the schemaAppliedProcessors section of your schema configuration. This involves specifying the processor name and entity.

Supported Data Types

  • String
  • Double
  • Decimal
  • Integer
  • Json
  • BLOB
  • Boolean

Config Requirements

Config ({}) options are required for the TRIGGER REPROCESS processor. If no configuration is provided or if the configuration is improperly set up, a block violation will be thrown. For more information on Apiro violations and their appearance in the Apiro UI or logs, refer to the violations section.

Example Config

Below is an example of how to configure the TRIGGER REPROCESS processor in XML format:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
<schemaAppliedProcessors>
    <dataBlockProcessors>
        <dataBlockProcessor name="BLOCK_TRIGGER_REPROCESS" entity="TRIGGER_REPROCESS">
            <config>
                <![CDATA[
                    {
                        "schema":"ASX_200_LIST",
                        "all":"true"
                    }
            ]]>
            </config>
        </dataBlockProcessor>
    </dataBlockProcessors>
</schemaAppliedProcessors>

Example Result

Upon successful configuration and execution, the TRIGGER REPROCESS processor will initiate the reprocessing of data within the specified schema (ASX_200_LIST). The "all":"true" configuration indicates that all data within the schema should be reprocessed.

Config Parameters

name acceptable values comment
schema A string representing the name of the schema for which data reprocessing is to be triggered
all A boolean indicating whether all data within the specified schema should be reprocessed. If set to "true", all data will be reprocessed; otherwise, specific data may be targeted for reprocessing

Common Mistakes

  • Ensure that the processor name and entity are correctly defined in the configuration to ensure that the processor is correctly identified and applied during the data processing pipeline.
  • Verify that the schema name matches an existing schema in your data processing environment.
  • Ensure that the all parameter is correctly set to either "true" or "false" based on whether you intend to reprocess all data within the schema or target specific data for reprocessing.
  • Remember that the configuration for the TRIGGER REPROCESS processor is required. If no configuration, or improper configuration is provided then a block violation will be thrown.