如何为每个“记录"类型字段摆脱BigQuery表中的__key__列? [英] How to get rid of __key__ columns in BigQuery table for every 'Record' Type field?

本文介绍了如何为每个“记录"类型字段摆脱BigQuery表中的__key__列?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

对于我的Firestore表的每个记录"类型,BigQuery都会自动添加""列.我不想为每个记录"类型字段添加这些内容.如何摆脱BigQuery自动添加的这些额外的列? (我想摆脱以黄色突出显示的BigQuery表架构中的以下列)

For every 'Record' Type of my Firestore table, BigQuery is automatically adding the 'key' columns. I do not want to have these added for each of the 'Record' Type fields. How can I get rid of these extra columns automatically being added by BigQuery? (I want to get rid of the below columns in my BigQuery table schema highlighted in yellow)

推荐答案

这是预期的行为,引用了Bigquery GCP

This is intended behavior, citing Bigquery GCP documentation:

Firestore 中的每个文档都有一个唯一的密钥,其中包含 信息,例如文档ID和文档路径.大查询 为密钥创建一个RECORD数据类型(也称为STRUCT), 每个信息都带有嵌套字段,如 下表.

Each document in Firestore has a unique key that contains information such as the document ID and the document path. BigQuery creates a RECORD data type (also known as a STRUCT) for the key, with nested fields for each piece of information, as described in the following table.

由于Firestore导出方法与GCP管理的导入和导出完全集成,因此

Due to the fact that Firestore export method is fully integrated with GCP managed import and export service, you can't change this behavior, excluding __key__.* properties being sent for each RECORD field in the target Bigquery table.

我猜在您的用例中,Bigquery表修改操作将需要一些动手干预,因为它需要手动更改架构数据.

I guess in your use case, Bigquery table modification action will require some hand-on intervention, since it requires manually changing schema data.

为了设置这种可行性,我鼓励您通过Google公开发行 tracker向供应商提出服务请求.

In order to set up this feasibility I would encourage you to raise a service request to the vendor via Google public issue tracker.

这篇关于如何为每个“记录"类型字段摆脱BigQuery表中的__key__列?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆