You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/storage/catalog/bigquery/index.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,10 +87,10 @@ from <project-id>.<source-name>.<collection-name>$20160809
87
87
#### Views
88
88
89
89
A [view](https://cloud.google.com/bigquery/querying-data#views) is a virtual
90
-
table defined by a SQL query. We use views in our de-duplication process to
90
+
table defined by a SQL query. Segment uses views in the de-duplication process to
91
91
ensure that events that you are querying unique events, and the latest objects
92
-
from third-party data. All our views are set up to show information from the last
93
-
60 days. Whenever possible, we recommend that you query from these views.
92
+
from third-party data. All Segment views are set up to show information from the last
93
+
60 days. Whenever possible, query from these views.
94
94
95
95
Views are appended with `_view` , which you can query like this:
96
96
@@ -125,7 +125,7 @@ Then, head to your warehouse's connection settings and update with the
125
125
126
126
BigQuery charges based on the amount of data scanned by your queries. Views are
127
127
a derived view over your tables that Segment uses for de-duplication of events.
128
-
Therefore, we recommend you query a specific view whenever possible to avoid
128
+
Therefore, Segment recommends you query a specific view whenever possible to avoid
129
129
duplicate events and historical objects. It's important to note that BigQuery
130
130
views are not cached.
131
131
@@ -154,12 +154,11 @@ querying sub-sets of tables.
154
154
Absolutely! You will just need to modify one of the references to 60 in the view
155
155
definition to the number of days of your choosing.
156
156
157
-
We chose 60 days as it suits the needs of most of our customers. However,
157
+
Segment chose 60 days as it suits the needs of most customers. However,
158
158
you're welcome to update the definition of the view as long as the name stays
159
159
the same.
160
160
161
-
Here is the base query we use when first setting up your views. We are leaving
162
-
in the placeholders (`%s.%s.%s`) where you would want to include the project,
161
+
Here is the base query Segment uses when first setting up your views. Included in the base query are the placeholders (`%s.%s.%s`) where you would want to include the project,
163
162
dataset and table (in that order).
164
163
165
164
```sql
@@ -198,7 +197,7 @@ functions.
198
197
### Does Segment support streaming inserts?
199
198
200
199
Segment's connector does not support streaming inserts at this time. If you have
201
-
a need for streaming data into BigQuery, [contact us](https://segment.com/requests/integrations/).
200
+
a need for streaming data into BigQuery, [contact Segment support](https://segment.com/requests/integrations/).
202
201
203
202
### Can I customize my sync schedule?
204
203
@@ -210,5 +209,5 @@ a need for streaming data into BigQuery, [contact us](https://segment.com/reques
210
209
211
210
### I'm seeing duplicates in my tables.
212
211
213
-
This behavior is expected. We only de-duplicate data in your views. See the
212
+
This behavior is expected. Segment only de-duplicates data in your views. See the
0 commit comments