Sensitive Data Protection fixes BigQuery timestamp bug
datagcpengineergcp-bigquery
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
Related releases
- Config Connector 1.154.1 Adds New Alpha Resources and Field Support Google Cloud release notes ·
- Google Cloud AI Infrastructure and Orchestration Updates - July 2026 Google Cloud Blog ·
- Data Studio Conversational Analytics GA, adds BigQuery integration Google Cloud release notes ·
- Cortex Framework v7 GA with modular architecture, Dataform, and AI features Google Cloud release notes ·
- BigQuery: Audit UI query result downloads Google Cloud release notes ·
- BigQuery Data Transfer Service adds incremental Klaviyo transfers Google Cloud release notes ·