-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow dates formatted as YYYYMMDD to be displayed as a datetime #338
Comments
@mreid So we've been going around and around on this one... part of the problem is that they don't want to accept this upstream, bc it's effectively impossible to reliably distinguish btn a YYYYMMDD formatted date string and an 8 digit number string that isn't meant to represent a date. We were thinking maybe we could add a view in the db layer that would perform the tranformation from YYYYMMDD to YYYY-MM-DD before the data gets to redash. Do you think this would be possible? |
Can we make it work as expected only when you explicitly pick "Datetime" Scale representation? That doesn't currently work either, and leaving the default representation as is would avoid problems with other 8-digit numeric strings (which I would expect to use some other representation, I usually use "Category" as a workaround, but could imagine Linear/Logarithmic being useful). |
That might be possible... we'll look into it. |
Progress here: getredash#3150 |
Confirmed that this is now fixed in stmo: https://sql.telemetry.mozilla.org/queries/50014/source#135495 |
Issue Summary
Mozilla uses YYYYMMDD date format in a bunch of places, primarily in our representation of "submission date". When used on the x-axis of a chart, the system defaults to interpreting it as a datetime (see #228). The resulting chart almost works, but requires a change to categorical before data will be displayed properly. In contrast to #228, we could actually interpret these values as dates to make things work with the default settings, we would need to detect and parse them differently.
Steps to Reproduce
Note the current workaround is to re-format the data as "YYYY-MM-DD", which is interpreted as expected.
The text was updated successfully, but these errors were encountered: