Amazon Redshift
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 redshift
What it is
An Amazon Redshift cluster. In the test estate it holds freight analytics: shipment cost and delivery facts in schema analytics.
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 | redshift |
| Other spellings that resolve | amazonredshift, awsredshift |
| Settings | host, port, database, username, ssl_mode |
| Credentials | password |
The test connection
Quillmere analytics (Redshift)
| Setting | Test value |
|---|---|
host | redshift.quillmere.invalid |
port | 5439 |
database | analytics |
username | face_reader |
ssl_mode | require |
Credentials: password. 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
redshift.zipand unzip it. It holdsredshift/01_schema.sql,redshift/02_data.sqlandredshift/expected.json, in the engine’s own dialect. - Run
01_schema.sql, then02_data.sql, in Query editor v2 on a cluster or serverless workgroup you own. - Add the connection with the settings above, pointed at your own cluster.
What FACE finds
FACE has no Redshift reader. A redshift connection is stored and resolves in the catalogue. The expected model is what a Postgres-wire information_schema read returns for this dataset.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
analytics.fact_shipment_cost | table | freight_audit | shipment_id | 24 | 6 |
analytics.fact_delivery | table | shipments | shipment_id | 24 | 6 |
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 5 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 |
|---|---|---|
| carrier | fact_shipment_cost.carrier_id | d365, document, files, guidewire, mysql, objectstore, postgres, sharepoint, tms, yms |
| customer | fact_delivery.customer_id | files, hubspot, kafka, oms, postgres, salesforce, sap, snowflake |
| invoice | fact_shipment_cost.invoice_id | d365, files, mysql, objectstore |
| shipment | fact_delivery.shipment_id, fact_shipment_cost.shipment_id | bigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, salesforce, sap, servicenow, sharepoint, tms, whs, yms |
| warehouse | fact_delivery.warehouse_id | inventory, oms, postgres, tms, whs, yms |
It holds no evidence for the six planted anomalies. It is context: it makes the shared keys resolve.
See all connectors at once for the walkthrough across every source.
Download
redshift.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
redshift/01_schema.sqlredshift/02_data.sqlredshift/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.