If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

DQF Configuration

The following article describes how Data Quality Firewalls (DQF) configuration can be customized in on-premise deployments.

All properties mentioned in the article are supplied through the /opt/ataccama/one/dqf-${DQF_VERSION}/etc/application.properties file.

DQ Firewall and MinIO bucket communication

By default, DQF cannot communicate with any MinIO buckets. To configure which buckets are accessible in component rules, add the following configuration to /opt/ataccama/one/dqf-${DQF_VERSION}/etc/application.properties:

# Resources definition
# Component rules can reference external resource via resource://<name>/<objectName>
# This configuration provides mapping between URLs and actual files

# Name of the resource used in URL
com.ataccama.dqf.runtimeResources[0].name=minio
# What storage should be used for this resource
# Has to reference existing ataccama.one.object-storage.storages[*].storage-id
com.ataccama.dqf.runtimeResources[0].storageId=minio
# Bucket name
com.ataccama.dqf.runtimeResources[0].bucket=lookup

Multiple resources can be added. In the previous example, you could add a second resource, for example:

com.ataccama.dqf.runtimeResources[1].name=minio
com.ataccama.dqf.runtimeResources[1].storageId=minio
com.ataccama.dqf.runtimeResources[1].bucket=shared

Index sequence must be continuous (no gaps).

This configuration is very similar to what you configure in DPM runtime configuration. In almost all cases, those configurations should be kept in sync so the same resources can be used in DQF and in DPE processing.

Was this page useful?