feat: Turn active_users_aggregates Looker view into a derived_table to enable parameterisation #984
Conversation
…o enable parameterisation
|
Is it safe to make this changes to the existing view? Is it worth considering adding a new |
|
Looker docs say that it doesn't automatically regenerate derived tables and would use cache (for ex. if no persistent is defined like in this case) which would not show real-time results (which unfortunately has been problematic in the past), To remove the risk, did you consider building a separate view for this derived table or using a PDT? |
@bochocki so generally this should recreate what already exists. So nothing should break. The idea behind recreating this resource is that the changes automatically get applied to all existing Looker resources so no additional work is required. There is an alternative approach that we could consider, this would include adding an additional field in the view, let's call it |
|
@lucia-vargas-a thanks for pointing this out. I was not aware of this Looker thing. I created a PR to pursue an alternative approach here: mozilla/bigquery-etl#6706 |
We should waiting for merging of this change until after 15th December due to ongoing KPI evaluations.
feat: Turn active_users_aggregates Looker view into a derived_table to enable parameterisation
Unfortunately, it appears this is the only way for us to enable a simple drop down filter on the distribution for the end user.