Hi Team, We are interested in how we can best capture Bigquery Routines (user defined functions /procedures written in SQL) in Collibra. We do have a bigquery driver setup to auto register bigquery metadata and lineage into Collbira. However, it was noted that routines are not registered automatical

There is a warning about Big Query and the Spark version being prior to 3: However… The customer was on Spark 3.1 and yet still needed to set a Collibra DQ Connector property for Big Query using the flag: dq.bq.legacy=true Then it worked! Brian Mearns had this to say about that:"dq.bq.leg

Is there a reason this is not available for download despite it being listed? There’s no download option only and

What GCP permissions do I require to harvest metadata from Big Query using the Spring Boot connector? I would like to be able to set these permissions programatically at the dataset level rather than giving wide ranging access at the project level.

Hello, i am trying to create some data sources in the DGC catalog for a Google BigQuery database. I have downloaded the Certified driver on the marketplace (it is a CData driver) I have created the specific form for the mandatory driver connection properties : DatasetId ProjectId Schema (same as Pr

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

Customer question: Are there any plans to support nested fields in BigQuery (array is not supported right now) and make the structs representation more user friendly? Answer from Brian Mearns:“At this time any nested, explode, flatten functionality is best handled by the JDBC interface layer

Question: How do I ensure my Collibra DQ BigQuery (“BQ”) Connection will work?Answer: There were three BQ connections, with three different Auth JSON files. I took Brian Mearns’ advice: “This is likely due to an updated handling of bigquery tables. The root cause (in my estim