Page MenuHomePhabricator

Bug: 'Include Time' option in table visualization produces "0NaN-NaN-NaN NaN:NaN:NaN"
Closed, ResolvedPublicBUG REPORT

Assigned To
Authored By
mpopov
Jun 23 2020, 2:56 PM
Referenced Files
F32368850: Screen Shot 2020-09-30 at 9.22.59 AM.png
Sep 30 2020, 1:25 PM
F31914481: jiggy.gif
Jul 2 2020, 6:40 PM
F31914465: batman.jpg
Jul 2 2020, 6:32 PM
F31876446: Superset bug 1.png
Jun 23 2020, 2:56 PM
F31876448: Superset bug 2A.png
Jun 23 2020, 2:56 PM
F31876456: Superset bug 3.png
Jun 23 2020, 2:56 PM

Description

Steps to Reproduce:

  1. Create a new chart from a data source like edits_hourly or druid.edits_hourly
  2. Choose table visualization and pick any kind of granularity
  3. Check 'Include Time' in the GROUP BY section
  4. Run query

Actual Results:

Superset bug 1.png (1×3 px, 643 KB)
Superset bug 2A.png (1×3 px, 640 KB)

Expected Results:

Since __time is a dimension in the druid.edits_hourly data source, we can include it manually as a dimension to GROUP BY. The __time column is what the Time column should look like:

Superset bug 3.png (1×3 px, 686 KB)

Related Objects

Event Timeline

mpopov moved this task from Inbox to Tracking on the Better Use Of Data board.
mpopov moved this task from Triage to Tracking on the Product-Analytics board.

@mpopov weird find. This sounds like an upstream superset bug. Could you make an issue with them? https://github.com/apache/incubator-superset/issues

Filed: https://github.com/apache/incubator-superset/issues/10203

The bug report template asks for python stacktraces from superset logs, which I don't have access to. I pinged @elukey on the issue, maybe he can provide the necessary info?

mpopov claimed this task.

The upgrade to 0.37.2 has fixed the issue

Screen Shot 2020-09-30 at 9.22.59 AM.png (1×2 px, 329 KB)