Skip to content

Commit 0623393

Browse files
Merge pull request #6015 from segmentio/bq-partition-expiration
Add BQ dataset's partition expiry
2 parents a03b50f + bae7d8d commit 0623393

File tree

1 file changed

+7
-1
lines changed
  • src/connections/storage/catalog/bigquery

1 file changed

+7
-1
lines changed

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,4 +220,10 @@ a need for streaming data into BigQuery, [contact Segment support](https://segme
220220

221221
### I see duplicates in my tables.
222222

223-
This behavior is expected. Segment only de-duplicates data in your views. Refer to the [schema section](#schema) for more details.
223+
This behavior is expected. Segment only de-duplicates data in your views. Refer to the [schema section](#schema) for more details.
224+
225+
### Why does some of my older BigQuery data expire?
226+
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.
228+
229+
You can safely change the default table expiration to ‘Never’, which removes these expirations from the tables/dataset and changes the dataset's default table expiration. Segment can then run a backfill for you and send all of your historical data to your warehouse.

0 commit comments

Comments
 (0)