Skip to content

MOCK ANONYMISE

Description

The MOCK ANONYMISE processor is designed for testing and development purposes. It simulates the process of anonymising data without actually performing any real anonymisation. This processor is particularly useful for scenarios where you need to test the data processing pipeline without affecting real data.


Config Location

To configure the MOCK ANONYMISE 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 not required for the MOCK ANONYMISE processor. This simplifies the configuration process, making it easier to integrate into existing data processing pipelines without the need for additional configuration parameters.


Example Config

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

1
2
3
4
5
6
7
<schemaAppliedProcessors>
    <dataBlockProcessors>
        <dataBlockProcessor name="BLOCK_MOCK_ANONYMISE" entity="MOCK_ANONYMISE">
            <config>{}</config>
        </dataBlockProcessor>
    </dataBlockProcessors>
</schemaAppliedProcessors>

This configuration is minimal, as no specific configuration options are required for this processor.


Config Parameters

Since config options are not required for the MOCK ANONYMISE processor, there are no specific configuration parameters to list.


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 MOCK ANONYMISE processor is intended for testing and development purposes only. It does not perform any real data anonymisation.