The subsession start date (and creation date) will break the from_iso8601_timestamp function. The subsession start date contains a time zone designator "[+|-]hh" outside of the [-12, 12] range.  https://sql.telemetry.mozilla.org/queries/49895/source
Timezones can be outside of the [-12, 12] range AFAIK: https://en.wikipedia.org/wiki/Time_zone#List_of_UTC_offsets Do you suspect a client issue here? Are there actual invalid timezones submitted? Or do we need a presto fix? Or dataset normalization as a workaround?
There are timezones out of those UTC offsets (+17, -19, etc). The workaround during query time is to use `date_parse(substr(___))`, but something in main_summary might be worthwhile to avoid the hassle involved with different date/time formats.
These are probably timezones clients are legitly reporting (from a Telemetry perspective), so i would suggest that we fix them up for derived datasets if needed. This would be good to document though for people that are interested in the real offsets clients see.
Component: Telemetry → Datasets: General
Product: Toolkit → Data Platform and Tools
Looks like the plan is to clean the data flowing into main_summary, so moving this bug to that component.
Component: Datasets: General → Datasets: Main Summary
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.