这是 Bigquery 的 Time Travel 的一个令人讨厌的、未记录的副作用。 Time Travel 使在 bigquery 中使用 ALTER TABLE 语句变得不安全。
问题演示:
create table apu.time_travel_problem
( id int64
, name string
);
select column_name, data_type
FROM apu.INFORMATION_SCHEMA.COLUMNS
WHERE table_name = 'time_travel_problem';
| column_name |
data_type |
| id |
INT64 |
| name |
STRING |
到目前为止这一切都很正常,但是在ALTER TABLE 之后一切都变得奇怪了:
alter table apu.time_travel_problem drop column name;
select column_name, data_type
FROM apu.INFORMATION_SCHEMA.COLUMNS
WHERE table_name = 'time_travel_problem';
| column_name |
data_type |
| id |
INT64 |
| name |
STRING |
我们刚刚删除的那一列还在!
现在试试这个:
alter table apu.time_travel_problem add column name string;
Column `name` was recently deleted in the table `time_travel_problem`. Deleted column name is reserved for up to the time travel duration, use a different column name instead.
解决方案:
不要在 bigquery 中使用 ALTER TABLE。而是 DROP 和 reCREATE 使用临时表。
这是我使用的jinja 模板:
/* {{TABLE}} */
CREATE TABLE IF NOT EXISTS {{DATASET}}.{{TABLE}}_migration
OPTIONS (expiration_timestamp = timestamp_add(CURRENT_TIMESTAMP(), INTERVAL 8 HOUR))
AS SELECT * FROM {{DATASET}}.{{TABLE}};
DROP TABLE {{DATASET}}.{{TABLE}};
CREATE TABLE {{DATASET}}.{{TABLE}}
(
{{COLUMN_DDL}}
);
INSERT INTO {{DATASET}}.{{TABLE}}
(
{{COLUMN_LIST}}
)
SELECT
{{COLUMN_LIST}}
FROM {{DATASET}}.{{TABLE}}_migration;