Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Update BigQuery batch exports schema #10018

Merged
merged 1 commit into from
Dec 2, 2024
Merged

Docs: Update BigQuery batch exports schema #10018

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions contents/docs/cdp/batch-exports/bigquery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,8 @@ Navigate to IAM and click on Grant Access to arrive at this screen:

This section describes the models that can be exported to BigQuery.

> **Note:** New fields may be added to these models over time. To maintain consistency, these fields are not automatically added to the destination tables. If a particular field is missing in your BigQuery tables, you can manually add the field, and it will be populated in future exports.

### Events model

This is the default model for BigQuery batch exports. The schema of the model as created in BigQuery is:
Expand Down Expand Up @@ -99,6 +101,7 @@ The schema of the model as created in BigQuery is:
| properties | `STRING` or `JSON` | A JSON object with all the latest properties of the person |
| person_version | `INT64` | Internal version of the person properties associated with a (`team_id`, `distinct_id`) pair, used by batch export in merge operation |
| person_distinct_id_version | `INT64` | Internal version of the person to `distinct_id` mapping associated with a (`team_id`, `distinct_id`) pair, used by batch export in merge operation |
| created_at | `TIMESTAMP` | The timestamp when the person was created |

The BigQuery table will contain one row per `(team_id, distinct_id)` pair, and each pair is mapped to their corresponding `person_id` and latest `properties`. The `properties` field can be either `STRING` or `JSON`, depending on whether the corresponding checkbox is marked or not when creating the batch export.

Expand Down