New York Times to Google BigQuery Integration
AI-first ETL from New York Times into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads New York Times into Google BigQuery
Datrise syncs New York Times's articles, sections, headlines, bylines, publication dates, and keywords into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.
Ideal for Google-stack analytics and ML on serverless infrastructure.
Endpoints
New York Times: Article archive and top-stories metadata.
Google BigQuery: Serverless analytics warehouse on GCP.
How New York Times entities map to Google BigQuery
| New York Times entity | Google BigQuery object | Notes |
|---|---|---|
| articles | new_york_times_articles | id PK · custom fields → JSON or nested/repeated (STRUCT) columns |
| sections | new_york_times_sections | id PK · linked to new_york_times_articles |
| headlines | new_york_times_headlines | id PK · linked to new_york_times_articles |
| bylines | new_york_times_bylines | id PK · linked to new_york_times_articles |
FAQ
How does Datrise handle New York Times's custom fields in Google BigQuery?
Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.
How does the New York Times to Google BigQuery sync stay up to date?
It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.
Related pipelines
More destinations for New York Times
- New York Times → Amazon Redshift
- New York Times → Databricks SQL Warehouse
- New York Times → ClickHouse
- New York Times → DuckDB
- New York Times → Amazon Athena
- New York Times → Amazon S3 Data Lake
- New York Times → Azure Data Lake Storage
- New York Times → Azure Synapse
- New York Times → Spreadsheets
- New York Times → Airtable
- New York Times → CSV Files
- New York Times → MongoDB
More sources for Google BigQuery
- News API → Google BigQuery
- Newsdata → Google BigQuery
- Notion → Google BigQuery
- Okta → Google BigQuery
- Omnisend → Google BigQuery
- Onesignal → Google BigQuery
- Onfleet → Google BigQuery
- Openweather → Google BigQuery
- Opsgenie → Google BigQuery
- Oracle Database → Google BigQuery
- Orb → Google BigQuery
- Orbit → Google BigQuery
Early access
Connect New York Times to Google BigQuery the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.