Introduktion till BigQuery
Matt Forrest
Field CTO
Det finns tre huvudsakliga optimeringsregler:
SELECT * – välj bara de kolumner du behöverWHERE-satsen tidigt och oftaINT64.WITH filter_my_data AS (SELECT
-- Filter data with
-- WHERE in the CTE first
)
SELECT
-- This query will run
-- faster with less data
JOIN a USING (user_id)
Använd i BigQuery
BOOLINTFLOATDATE Datatyperna WHERE, STRING och BYTE är inte optimala.
Inte optimalt
SELECT user_id, date_ordered
FROM dataset.table
WHERE product = 'shoes'
Optimalt
SELECT user_id, date_ordered
FROM dataset.table
WHERE product_id = 1234
ORDER BY ska alltid placeras ytterst (i slutet) av fråganORDER BY i en fönsterfunktionssatsInte optimalt
WITH order_total AS (SELECT
user_id,
sum(product_price) as order_sum
FROM orders
GROUP BY user_id
-- Order by is not at the end of the query
ORDER BY last_purchase_date
)
SELECT order_total.order_sum,
users.user_name
FROM dataset.users users
JOIN order_total USING (user_id);
Optimalt
WITH order_total AS (SELECT
user_id,
last_purchase_date
sum(product_price) as order_sum
GROUP BY user_id
)
SELECT order_total.order_sum,
users.user_name
FROM dataset.users users
JOIN a USING (user_id)
-- Order by should always be at the end
ORDER BY orders_total.last_purchase_date;
EXISTSCOUNT för detta ändamålSELECT EXISTS (
-- Write the main query as a subquery within the exists call
SELECT
user_id
FROM
dataset.table
WHERE
product_category = 'home_goods'
AND status = 'Closed Account'
);
APPROX_TOP_SUM eller APPROX_COUNT_DISTINCT.WHERE-satsen.Introduktion till BigQuery