Skip to content

Commit 41e1ae5

Browse files
Apply suggestions from code review
1 parent 0fd668f commit 41e1ae5

File tree

1 file changed

+2
-2
lines changed
  • src/connections/storage/catalog/bigquery

1 file changed

+2
-2
lines changed

src/connections/storage/catalog/bigquery/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -222,8 +222,8 @@ a need for streaming data into BigQuery, [contact Segment support](https://segme
222222

223223
This behavior is expected. Segment only de-duplicates data in your views. Refer to the [schema section](#schema) for more details.
224224

225-
### BigQuery Default Partition Expiration
225+
### Why does some of my older BigQuery data expire?
226226

227-
If you notice that your BigQuery data is getting deleted after a specific period of time, then it might be due to a [dataset's default table expiration](https://cloud.google.com/bigquery/docs/updating-datasets#partition-expiration) in BigQuery that sets a 90-day (or similar) expiration on all partitioned tables that are created.
227+
If you notice that you are missing older BigQuery data, it might be due to a [dataset's default table expiration](https://cloud.google.com/bigquery/docs/updating-datasets#partition-expiration){:target="_blank”} in BigQuery. The default table expiration sets a standard expiration on all partitioned tables that are created.
228228

229229
However, you can safely remove these expirations from the tables/dataset and change them to ‘Never’, and change the dataset's default table expiration as needed. We will then be able to run a backfill for you to send all the historical data to your warehouse.

0 commit comments

Comments
 (0)