GCP allows us to create Images. These images contain the configuration for creating instances. You can launch multiple instances from a single image when you need multiple instances with the same configuration. This post explains how to configure Collibra DQ from a GCP image with DQ installed. Click

hello, I am configuring a BigQuery Technical Lineage, but I have realized that in the section "other queries" the tables from information schema used is not the same from the default collibra query : SELECTr.routine_name,CONCAT('CREATE ', r.routine_type, ' `', r.routine_schema, '.', r.routine_name

Hi Team, We are using Google Big Query to Collibra integration using the JDBC driver , We are able to ingest schema details however we would like to ingest additional information like below Table Type Partitioned by Partitioned on field Can you please let us know if there is any process to get the

A startup script is a file that performs tasks during the startup process of a virtual machine (VM) instance. We are going to configure our DQ instance to be able to start Collibra DQ (Postgre, Spark, OwlAgent OwlWebapp) automatically when the instance is started. For more information about how this

Question: Dataproc architecture & sizing. We are considering multi-tenancy with Collibra DQ – having different teams in the tool running their own data profiling jobs. We’re working on our Prod sizing, so can we have different Dataproc clusters running, one for each tenant? If yes, how can we

Hello, We are building GCP Technical Lineage using the capability from Edge. Please let me know if there a workaround to stich the stored procedures / routines from GCP and have the technical lineage available. Thank you, Ionut Filoti