Firebase中的BigQuery集成反复返回409 [英] BigQuery integration in Firebase repeatedly returns 409

查看:70
本文介绍了Firebase中的BigQuery集成反复返回409的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我设置了一个Firebase项目,该项目将其数据连续导出到BigQuery(使用标准的UI集成)-每天自动创建一个新的events_intraday_*表.

I have a Firebase project set up that continually exports its data to BigQuery (using the standard UI integration) - automatically creating a new events_intraday_* table each day.

但是,Firebase在白天一直尝试创建表-即使已经创建了该表-也会导致状态码409.

However, Firebase keeps trying to create the table during the day - even though it's already been created - which results in status code 409.

这可能是角色/权限问题吗?我在BQ中的Firebase服务帐户仅具有标准的Editor角色.

Could this be a role/permission issue? My Firebase service account in BQ only has the standard Editor role.

推荐答案

我联系了Firebase支持人员,并得到以下答复:

I contacted Firebase support and got the following response:

这实际上是一些检查的结果,以确保数据集正常且可操作.我同意这会使活动日志变得嘈杂并且难以阅读.我们正在寻找潜在的解决方案来解决此问题,但是目前我没有可以分享的任何具体细节或时间表.

This is actually a result of some checks to ensure that the dataset is fine and operational. I agree that this makes the activity logs noisy and hard to read though. We're looking into potential solutions to address this, but I don't have any specific details or timelines I can share at this time.

因此,这似乎是一个已知但无害的问题.

So it appears that it is a known, but harmless, issue.

这篇关于Firebase中的BigQuery集成反复返回409的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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