【发布时间】:2018-08-23 16:09:49
【问题描述】:
我针对我们的移动应用数据编写了以下查询。由于用户群较高,当我在底部添加 ORDER BY 时,我收到 400 请求错误 "Resources exceeded during query execution: The query could not be executed in the allotted memory"。
问题:我可以做些什么来优化查询,但仍保留底部的ORDER BY?
我已经在 firebase 的演示数据集中添加了,但我认为他们的数据集太小了,不会有问题(与我的数据集相比,它有 5-10 百万条记录)。
SELECT
f.user_pseudo_id,
f.event_timestamp,
DATE(TIMESTAMP_MICROS(f.event_timestamp)) as event_timestamp_date,
f.event_name,
f.user_first_touch_timestamp,
DATE(TIMESTAMP_MICROS(f.user_first_touch_timestamp)) as user_first_touch_date,
CASE WHEN r.has_appRemove >= 1 THEN "removed" ELSE "not-removed" END AS status_after_first7days
FROM `firebase-analytics-sample-data.ios_dataset.app_events_*` f
LEFT JOIN (
SELECT user_pseudo_id, 1 has_appRemove
FROM `firebase-analytics-sample-data.ios_dataset.app_events_*`
WHERE DATE(TIMESTAMP_MICROS(user_first_touch_timestamp)) >= DATE_SUB(CURRENT_DATE(), INTERVAL 10 DAY)
AND DATE(TIMESTAMP_MICROS(user_first_touch_timestamp)) < DATE_SUB(CURRENT_DATE(), INTERVAL 9 DAY)
AND _TABLE_SUFFIX >= FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 10 DAY))
AND _TABLE_SUFFIX < FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 3 DAY))
AND platform = "ANDROID"
AND event_name = "app_remove"
GROUP BY user_pseudo_id
) r on f.user_pseudo_id = r.user_pseudo_id
WHERE
DATE(TIMESTAMP_MICROS(user_first_touch_timestamp)) >= DATE_SUB(CURRENT_DATE(), INTERVAL 10 DAY)
AND DATE(TIMESTAMP_MICROS(user_first_touch_timestamp)) < DATE_SUB(CURRENT_DATE(), INTERVAL 9 DAY)
AND _TABLE_SUFFIX >= FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 10 DAY))
AND _TABLE_SUFFIX < FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 3 DAY))
AND platform = "ANDROID"
ORDER BY 1,2 ASC
【问题讨论】:
-
这会产生多少行?你可以使用限制吗? cloud.google.com/bigquery/docs/…
-
嗨,Elliot,很遗憾,我不能应用 LIMIT,因为我正在使用此查询将数据写入长期表(每天通过 bigquery 任务调度程序)。我使用了 Mikhail 的分区答案,它完成了工作:)
-
太棒了!我很高兴米哈伊尔的回答对你有用。请注意,如果您将结果写入另一个表,
ORDER BY是没有意义的,因为表不保留顺序;只有查询结果。
标签: firebase google-bigquery firebase-analytics http-status-code-400