CODEWITHSUNDEEP
cachinggoogle-bigquerymaterialized-viewsreal-time-data
Shushu
Shushu

Reputation: 792

Bigquery Materialized view billing - is there a 10mb minimum?

Looking into getting near-realtime analytics data from bigquery, and considering costs vs. accuracy, it seems like using materialized view might be a great win.
Considering "near real time" will change to a minimum of 1 minute refresh_interval_minutes, my main concern is that while from documentation it seems that the query will be only on the delta data, the billing will be on the "standard" minimum of 10MB per table.
As I see it, if this minimum is being forced, it dismiss using materialized view as a valid solution for near-realtime.

I would have used "standard" caching over the queries, but caching does not work when querying table with "buffered data", as far as I understand it.

Please advise,
Shushu

Upvotes: 3

Views: 2746

Answers (1)

Pentium10
Pentium10

Reputation: 208002

The following are key characteristics of BigQuery Materialized Views:

Zero maintenance: A materialized view is recomputed in background once the base table has changed. All incremental data changes from the base tables are automatically added to the materialized views. No user inputs are required.

In other words it means that incremental changes like streaming data into, is automatically added to the materialized view. That means you don't need to set 1 minute refresh period. The maximum refresh frequency cap is 7 days. You could set it to 7 days, or even disable manual refresh as you don't have deletes.

Upvotes: 0

Related Questions