Data connectors in HERE Anonymizer Self-Hosted

Data connectors facilitate reading data from data sources and writing data to data sinks. Sources and sinks can be databases, message queues, streaming platforms, etc. Some connectors support the management API which can be used to updated configuration and/or license during the runtime (in streaming mode only).

HERE Anonymizer Self-Hosted works with these types of data sources and data sinks:

Connector type	Batch mode	Streaming mode	Management API	Supports source compression	Supports sink compression
RabbitMQ	❌	✅	✅	✅	✅
Apache Kafka	❌	✅	❌	✅	✅
HERE platform stream layer	❌	✅	❌	✅	✅
Azure Blob Storage	✅	❌	✅	✅	✅
Azure Event Hubs	❌	✅	❌	✅	✅
AWS Kinesis	❌	✅	❌	✅	✅
AWS SQS	❌	✅	❌	✅	✅
AWS S3	✅	❌	✅	✅	✅

Connectors are responsible for connecting to sources or sinks. They don't define the input or output data format. Read this document to learn about the supported data formats.

Basic configuration

All connectors are configured through an URI string. The URI schema defines the connector type.

The generic URI syntax is [scheme:]scheme-specific-part[#fragment].

Please see the scheme-specific syntax for each supported connector type at:

SSL configuration

Connectors that support SSL require three PEM-format files:

Client key
Client certificate
CA certificates

The convention for using SSL in connectors is through query parameters:

keyFile: path to the client key file in PEM format
crtFile: path to the client certificate file in PEM format
caFile: path to the CA certificates file in PEM format

Data format auto-detection

The HERE platform stream layer connector supports data format auto-detection. The connector recognizes the input and output data format automatically, which means that you can set SOURCE_FORMAT and SINK_FORMAT to auto or leave the value empty.

📘
Note
To facilitate data format auto-detection, the queue hosting must be configured properly. Learn more here.