From c0813757b24486966f638a0552cb476f0e531ebc Mon Sep 17 00:00:00 2001 From: LRubin Date: Tue, 23 Feb 2021 16:16:06 -0800 Subject: [PATCH] Add helpful note about BigQuery --- src/connections/storage/warehouses/schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/storage/warehouses/schema.md b/src/connections/storage/warehouses/schema.md index de6416b742..28b1455718 100644 --- a/src/connections/storage/warehouses/schema.md +++ b/src/connections/storage/warehouses/schema.md @@ -25,7 +25,7 @@ The table below describes the schema in Segment Warehouses: `.users` - A table with unique `identify` calls. `identify` calls are upserted on `user_id` into this table (updated if an existing entry exists, appended otherwise). This table holds the latest state of a user. The `id` column in the users table is the same as the `user_id` column in the identifies table. Also note that this table won't have an `anonymous_id` column since a user can have multiple anonymousIds. To get at a user's anonymousIds, you'll need to query the identifies table. *If you observe any duplicates in the users table, [contact us](https://segment.com/help/contact/).* + A table with unique `identify` calls. `identify` calls are upserted on `user_id` into this table (updated if an existing entry exists, appended otherwise). This table holds the latest state of a user. The `id` column in the users table is the same as the `user_id` column in the identifies table. Also note that this table won't have an `anonymous_id` column since a user can have multiple anonymousIds. To get at a user's anonymousIds, you'll need to query the identifies table. *If you observe any duplicates in the users table [contact us](https://segment.com/help/contact/) (unless you are using Bigquery, where [this is expected](/docs/connections/storage/catalog/bigquery/#schema)).* `.pages`