Google BigQuery
change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.Grade D · dataset: SQL (DDL and rows in the engine’s dialect) · type bigquery
What it is
A Google BigQuery dataset. In the test estate it holds fleet history: GPS pings and planned routes in dataset fleet.
Grade
D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.
See the grade table for all 32 types.
Settings and credentials
From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.
| Names | |
|---|---|
| Type | bigquery |
| Other spellings that resolve | bq |
| Settings | project_id, dataset_id |
| Credentials | service_account_json |
The test connection
Quillmere fleet history (BigQuery)
| Setting | Test value |
|---|---|
project_id | quillmere-demo |
dataset_id | fleet |
Credentials: service_account_json. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.
Stand up the test system
The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.
- Download
bigquery.zipand unzip it. It holdsbigquery/01_schema.sql,bigquery/02_data.sqlandbigquery/expected.json, in the engine’s own dialect. - Run
01_schema.sql, then02_data.sql, inbq query --use_legacy_sql=falsein a project you own. The DDL names the projectquillmere-demo: replace it with your project id first. - Add the connection with the settings above, pointed at your own project and dataset.
What FACE finds
FACE’s BigQuery connector reports that it has no catalogue to read, rather than inventing one. The expected model is what INFORMATION_SCHEMA returns for this dataset.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
fleet.gps_pings | table | telematics | ping_id | 231 | 8 |
fleet.planned_routes | table | telematics | shipment_id, seq | 240 | 4 |
expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.
How it joins the Quillmere universe
This source carries 2 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.
| Universe entity | Fields here | Also in |
|---|---|---|
| device | gps_pings.device_id | cctv, databricks, files, gps, iot, kafka, mqtt, postgres, rfid, servicenow |
| shipment | gps_pings.shipment_id, planned_routes.shipment_id | d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms |
Evidence it holds for the planted anomalies:
- ANOM-5, A GPS route deviation.
bigquery/02_data.sqlinbigquery.zip, look for'PG-000205'(first off-corridor ping). - ANOM-5, A GPS route deviation.
bigquery/02_data.sqlinbigquery.zip, look for'SHP-50021'(the planned corridor).
See all connectors at once for the walkthrough across every source.
Download
bigquery.zip: 3 files,expected.jsonincluded.
This is one of 25 zips: the 7 streaming types ship as replay recordings instead.
What is in the zip
bigquery/01_schema.sqlbigquery/02_data.sqlbigquery/expected.json
The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.