You have a query that filters a BigQuery table using a WHERE clause on timestamp and ID columns. By using bq query "" -d
Posted: Mon Aug 01, 2022 9:51 am
You have a query that filters a BigQuery table using a WHERE clause on timestamp and ID columns. By using bq query "" -dry_run you learn that the query triggers a full scan of the table, even though the filter on timestamp and ID select a tiny fraction of the overall data. You want to reduce the amount of data scanned by BigQuery with minimal changes to existing SQL queries. What should you do?
A. Create a separate table for each ID.
B. Use the LIMIT keyword to reduce the number of rows returned.
C. Recreate the table with a partitioning column and clustering column. Most Voted
D. Use the bq query - -maximum_bytes_billed flag to restrict the number of bytes billed.
A. Create a separate table for each ID.
B. Use the LIMIT keyword to reduce the number of rows returned.
C. Recreate the table with a partitioning column and clustering column. Most Voted
D. Use the bq query - -maximum_bytes_billed flag to restrict the number of bytes billed.