Aggregate Awareness with Templated Filters or Parameters

[matt_jackman-16]

I'm looking to leverage Aggregate Awareness for our large tables. Our BigQuery database is partitioned by date, so we need to use a Date filter on all of our Explore queries. We've implemented this with the use of Templated filters and Parameters to enable a constant to be passed to the SQL to satisfy the BigQuery partition pruning requirements.

However, I'm running into limitations when trying to leverage Aggregate Awareness with PDTs.

I can't add a Templated Filter or Parameter to the 'dimensions' in an aggregate table, and if I add it to the 'filters' section, the Explore query date must exactly match the hardcoded 'filters' in the aggregate definition.

If I don't put either into the aggregate definition, it won't use the aggregate table because it doesn't have all of the fields used in the explore query.

Any suggestions?

[thomasrose]

That is something i am also HIGHLY interested