Skip to content

TRIGGER FEED

Description

The TRIGGER FEED processor is designed to cascade trigger a feed from another feed during the consolidation phase of data processing. This processor is particularly useful for creating dependencies between feeds, where the processing of one feed triggers the processing of another feed. It supports all data types, including BLOBs, making it versatile for various data processing needs.

Config Location

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

Supported Data Types

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

Config Requirements

Config ({}) options are required for the TRIGGER FEED 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 FEED processor in XML format:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
<dataPoint name="NAME" dataType="STRING">
    <consDPProcessors>
        <consDPProcessor name="TRIGGER_FEED_FROM_DP" entity="TRIGGER_FEED">
            <config>
                <![CDATA[
                    {
                        "entity": "ASX200_PRICING",
                        "config": {
                            "carryData": {
                                "CODE" : "#GRV{CTX['.']}"
                            },
                            "dataSource": {
                                "config": {
                                    "substitutions": {
                                        "CODE": "#GRV{CTX['.']}"
                                    }
                                }
                            }
                        }
                    }
                ]]>
            </config>
        </consDPProcessor>
    </consDPProcessors>
</dataPoint>

Example Result

  • upon successful configuration and execution, the TRIGGER FEED processor will trigger the processing of the specified feed ("ASX200_PRICING" in this example)
  • this allows for the cascading of data processing across multiple feeds.

Config Parameters

name acceptable values comment
entity A string representing the name of the feed to be triggered. This defines the feed that will be triggered.
config A JSON object specifying the configuration for the triggered feed. This includes any specific configurations required for the triggered feed.
carryData A JSON object specifying the data to be carried over to the triggered feed. This defines the data that will be passed to the triggered feed.
dataSource A JSON object specifying the data source configuration for the feed. This includes any specific data source configurations for the feed.
substitutions A JSON object specifying substitutions to be applied to the feed data. This defines any substitutions that will be applied to the feed data.

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 configuration parameters within the <config> tag are correctly written and match the expected format and values.
  • Remember that the configuration for the TRIGGER FEED processor is required. If no configuration, or improper configuration is provided then a block violation will be thrown.