Skip to content

TRIGGER FEED

Description

The TRIGGER FEED processor is designed to initiate the retrieval and processing of data feeds. This processor is particularly useful for scenarios where data needs to be fetched from external sources on a regular basis, such as financial market data, news feeds, or social media updates.

Config Location

To configure the TRIGGER FEED 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 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
<schemaAppliedProcessors>
    <dataBlockProcessors>
        <dataBlockProcessor name="BLOCK_TRIGGER_FEED" entity="TRIGGER_FEED">
            <config>
                <![CDATA[
                    {
                        "feedName":"ASX200_LIST",
                        "feedDef":"EXPR_HTML_FEED",
                        "feedConfig":
                        {
                          "url": "https://www.asx200list.com/",
                          "method": "GET"
                        }
                    }
                ]]>
            </config>
        </dataBlockProcessor>
    </dataBlockProcessors>
</schemaAppliedProcessors>

Example Result

Upon successful configuration and execution, the TRIGGER FEED processor will initiate the retrieval of the specified data feed (ASX200_LIST) from the provided URL (https://www.asx200list.com/) using the GET method. The processor will then process the retrieved data according to the defined feed definition (EXPR_HTML_FEED).

Config Parameters

name acceptable values comment
feedName A string representing the name of the data feed to be triggered
feedDef A string representing the definition of the data feed, which determines how the data is processed
feedConfig A JSON object containing configuration details for the data feed, such as the URL and method for retrieval

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 feedName and feedDef are correctly set up for your data feed requirements.
  • Ensure that the feedConfig contains the correct URL and method for retrieving the data feed.
  • 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.