NULL

Description

The NULL processor is a specialized post-aggregation processor designed to perform no operation on the data. It is primarily used for schema overrides where the data type needs to be explicitly set to NULL without altering the data itself. This processor supports all data types, including BLOBs, making it versatile for various data processing scenarios.

Config Location

To configure the NULL 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

String
Boolean
Json
Integer
Double
Decimal

Config Requirements

Config ({}) options are not required for the NULL processor. This processor is designed to perform no operation on the data, making it straightforward to use without additional configuration.

Example Config

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

<dataPoint name="NAME" dataType="STRING">
    <consDPProcessors>
        <consDPProcessor name="NULLABLE" entity="NULL"/>
    </consDPProcessors>
</dataPoint>

Example Result

Upon successful configuration and execution, the NULL processor will not alter the data in any way, effectively leaving the data unchanged. This can be useful in scenarios where the data type needs to be explicitly set to NULL for schema compatibility or other reasons.

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.
Remember that the NULL processor does not require any configuration. If you attempt to provide a <config> block, it will be ignored.