Closed
Bug 1393830
Opened 7 years ago
Closed 7 years ago
Windows 10 Client Distributions dashboard hasn't updated in weeks
Categories
(Data Platform and Tools :: General, enhancement, P1)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: harter)
References
()
Details
Looking at the dashboard, the charts at the top say they haven't been updated in 17 days and ones below for over a month. Is something stuck? When I try to manually refresh, I get an "Error running query: line 3:6: Failed analyzing stored view 'hive.default.build_distribution': Access Denied: Cannot create view default.windows_10_aggregate" error. Also, the column ordering on the "Release Channel Distribution" chart appears to have gotten mixed up. Would be great if we could fix that too.
Reporter | ||
Comment 1•7 years ago
|
||
Triage note - this is one I do look at regularly, so I would appreciate it being unbroken in a relatively short timeframe :)
Reporter | ||
Comment 2•7 years ago
|
||
Ryan, do you have cycles to look into this or can you redirect to someone who does?
Flags: needinfo?(rharter)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → rharter
Assignee | ||
Comment 3•7 years ago
|
||
Looks like virtual views may no longer be supported in STMO? Blake, do you know of any recent changes that may have caused this permissions issue? Looks like the windows_10_aggregates view [0] runs fine but downstream queries using the view fail [1]. [0] https://sql.telemetry.mozilla.org/queries/776/source [1] https://sql.telemetry.mozilla.org/queries/817/source
Flags: needinfo?(rharter) → needinfo?(bimsland)
Comment 4•7 years ago
|
||
This appears to be due to a permissions change with how we authorize access to particular hive tables, particularly that creating a view that references another view requires the GRANT_SELECT permission [1] which was not set. This has been added to the config and I was able to successfully run the query that refreshed the build_distribution view, currently running the other downstream queries to verify it works all the way through. [1] https://prestodb.io/docs/0.180/connector/hive-security.html#table-rules
Flags: needinfo?(bimsland)
Reporter | ||
Comment 5•7 years ago
|
||
Looks like things are mostly working now, except the patch adoption charts at the bottom are still broken with "Error running query: type of symbol 'expr_10471' is expected to be bigint, but the actual type is varchar" messages.
Flags: needinfo?(rharter)
Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(rharter)
Priority: -- → P1
Assignee | ||
Comment 6•7 years ago
|
||
This should now be fixed. There was a broken CAST in an upstream query due to a new type of errant data. Additionally, Presto now appears to have issues with a (now fixed) naming collision that was affecting line 3 of this query [1]. I filed Bug 1399532 to make this more maintainable. [1] https://sql.telemetry.mozilla.org/queries/779/source#table
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•1 year ago
|
Component: Redash (STMO) → General
You need to log in
before you can comment on or make changes to this bug.
Description
•