DAU forecasts PDT creation failing
Categories
(Data Platform and Tools :: General, defect, P1)
Tracking
(Not tracked)
People
(Reporter: frank, Assigned: frank)
References
Details
DAU forecasts are generated on the fly when needed. Right now though Looker thinks it can't even query them, rendering the KPI report unavailable: https://mozilla.cloud.looker.com/dashboards-next/101?Date=after+2021%2F01%2F01.
| Assignee | ||
Comment 1•4 years ago
|
||
PR: https://github.com/mozilla/looker-spoke-default/pull/90
This is a workaround that doesn't let us build new forecasts.
| Assignee | ||
Comment 2•4 years ago
|
||
Looker has indicated to me that Looker does not officially support Liquid in PDTs. There is a potential path to make this work again by switching the PDTs to use persist_for rather than sql_trigger_value, the former of which does not auto-create with the regenerator.
However, given that is a not-officially-supported path, my recommendation now is to simply remove the existing PDT creation code, switch to just using the existing forecasts, and if the set of queried dimensions does not exist in the forecast cache, we indicate that to the users (instead of creating it).
Comment 3•4 years ago
|
||
(In reply to Frank Bertsch [:frank] from comment #2)
However, given that is a not-officially-supported path, my recommendation now is to simply remove the existing PDT creation code, switch to just using the existing forecasts, and if the set of queried dimensions does not exist in the forecast cache, we indicate that to the users (instead of creating it).
This sounds right to me, I imagine that we have already cached nearly all of the forecasts that people would be interested in.
Comment 4•7 months ago
|
||
Hello,
The Mozilla Data Engineering organization is currently going through our extensive backlog, consisting of hundreds of issues stretching back for nearly 10 years. We've done a pass through all of the open bugzilla bugs and have identified and tagged the ones that we think are relevant enough to still need attention. The rest, including the bug with which this comment is associated, we are closing as "WONTFIX" in a single bulk operation.
If you feel we have closed this (or any) issue in error, please feel free to take the following actions:
- Reopen the bug.
- Edit the bug to add the string
[dataplatform](including the brackets) to theWhiteboardfield. (Note that you must edit theWhiteboard, not the similarly namedQA Whiteboard.)
Doing this will ensure that we see the bug in our weekly triage process, where we will decide how to proceed.
Thank you.
Description
•