Unable to use Group by with multiple entries with TIME-SERIES TABLE

[guoxin-li]

Issue
This issue has been seen in superset 0.26, 0.35, and the latest version of 0.36. When queries with more than one entires of Group by for Time-Series Table, the following error is showing up :
Unexpected Error keys must be str, int, float, bool or None, not tuple

How to reproduce this Error:
Use any available data source to create a TIME-SERIES TABLE, add more than one Group by entries and run query

Trace log
Traceback (most recent call last): File "/opt/superset/venv/lib/python3.6/site-packages/superset/views/base.py", line 120, in wraps return f(self, *args, **kwargs) File "/opt/superset/venv/lib/python3.6/site-packages/superset/utils/decorators.py", line 69, in wrapper return f(*args, **kwargs) File "/opt/superset/venv/lib/python3.6/site-packages/superset/views/core.py", line 1092, in explore_json viz_obj, csv=csv, query=query, results=results, samples=samples File "/opt/superset/venv/lib/python3.6/site-packages/superset/views/core.py", line 1014, in generate_json return data_payload_response(*viz_obj.payload_json_and_has_error(payload)) File "/opt/superset/venv/lib/python3.6/site-packages/superset/viz.py", line 478, in payload_json_and_has_error return self.json_dumps(payload), has_error File "/opt/superset/venv/lib/python3.6/site-packages/superset/viz.py", line 470, in json_dumps obj, default=utils.json_int_dttm_ser, ignore_nan=True, sort_keys=sort_keys File "/opt/superset/venv/lib64/python3.6/site-packages/simplejson/_init_.py", line 412, in dumps **kw).encode(obj) File "/opt/superset/venv/lib64/python3.6/site-packages/simplejson/encoder.py", line 296, in encode chunks = self.iterencode(o, _one_shot=True) File "/opt/superset/venv/lib64/python3.6/site-packages/simplejson/encoder.py", line 378, in iterencode return _iterencode(o, 0) TypeError: keys must be str, int, float, bool or None, not tuple

[kamalkeshavani-aiinside]

@junlincc Please add appropriate tag to this issue.
I can reproduce this issue still in v1.1.0 and master.

[tugra-alp]

This issue is still exist in v1.3.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[grzesuav]

seen that on 1.4

[emgoryaynova]

Still exists in 2.0.1

[jinyangzhen]

yes, still exists in 2.0.1. Any plan to fix

[mtrentz]

Also had the same problem with the same error.

The result query runs fine in postgres.

[billcrook]

I see this in 3.0.1 with a time-series table chart.

[rusackas]

This obviously isn't getting much traction, as it doesn't seem to be ruining the day of any core committers. I'm tempted to close it since it's over three years old, but I'm guessing it still exists. Anyone on this thread willing to open a PR?

[Aset-21]

It would be cool to fix this error in the time-series table chart.

[kyledufrane]

still exists in 2.1.3

[rusackas]

2.x is no longer supported. We currently support 3.1 and 4.0. Can anyone confirm the issue still exists in supported versions?

[tfzrch]

still exists in 4.0.1

[VikramKumarArammeem]

@rusackas Same issue still facing with 3.1.2