Setting BigQuery region - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
dis_mcp
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
platform_spatial_analytics
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Precisely MCP
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

If you are using BigQuery targets, configure the dataset region before migrating projects.

  1. Edit the ConfigMap by using the command for your installation.

    Agents installed in June 2026 or later

    /usr/local/bin/k3s kubectl edit configmap connect-cdc-config

    Agents installed between February and June 2026

    /usr/local/bin/k3s kubectl edit configmap -n precisely-connect-cdc-ns connect-cdc-config

    Agents installed before February 2026

    sudo KUBECONFIG=/home/k3s/.kube/k3s.yaml /usr/local/bin/k3s kubectl edit configmap -n precisely-connect-cdc-ns connect-cdc-config
  2. Locate and uncomment the following property: 
    global.cdwh.bigquery.dataset.region=<region>
  3. Replace <region> with your BigQuery region. For example: 
    global.cdwh.bigquery.dataset.region=us-east4

This configuration causes all migrated projects on this agent to use the correct region setting.