Sensitive Data Protection fixes BigQuery timestamp bug
datagcpengineer
patch
Sensitive Data Protection has resolved a bug where some BigQuery table data profiles incorrectly showed a 1970 timestamp instead of NULL for non-expiring tables. This fix ensures accurate expiration time representation in saved table data profiles. The issue affected exports generated between July 2025 and June 2026, and new exports will now display correct timestamps.
Fixes (1) ›
- Sensitive Data Protection
Between July 2025 and June 2026, some table data profiles saved to BigQuery contained an incorrect 1970-01-01 timestamp instead of NULL in expiration_time for tables that don't expire. This issue has been fixed. New exports of table data profiles show the correct expiration timestamps.
Read the original announcement →
https://docs.cloud.google.com/release-notes#June_22_2026