You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/08/27 20:30:45 UTC
[GitHub] [superset] kevin-struckhoff opened a new issue #16487: Unexpected Error - Out of bounds nanosecond timestamp
kevin-struckhoff opened a new issue #16487:
URL: https://github.com/apache/superset/issues/16487
This is a follow on to Issue #16486, using the same dataset and table/data. I changed the chart type to 'Line Chart' and then pressed the 'Run' button. This error Message was displayed: 'Unexpected error Out of bounds nanosecond timestamp: 1-01-01 00:00:00'. Additionally, this stack trace info is from clicking on the 'see more' button:
Traceback (most recent call last):
File "/root/venv/lib64/python3.8/site-packages/pandas/core/arrays/datetimes.py", line 2085, in objects_to_datetime64ns
values, tz_parsed = conversion.datetime_to_datetime64(data)
File "pandas/_libs/tslibs/conversion.pyx", line 350, in pandas._libs.tslibs.conversion.datetime_to_datetime64
TypeError: Unrecognized value type: <class 'str'>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/root/venv/lib64/python3.8/site-packages/superset/viz.py", line 540, in get_df_payload
df = self.get_df(query_obj)
File "/root/venv/lib64/python3.8/site-packages/superset/viz.py", line 288, in get_df
utils.normalize_dttm_col(
File "/root/venv/lib64/python3.8/site-packages/superset/utils/core.py", line 1692, in normalize_dttm_col
df[DTTM_ALIAS] = pd.to_datetime(
File "/root/venv/lib64/python3.8/site-packages/pandas/core/tools/datetimes.py", line 805, in to_datetime
values = convert_listlike(arg._values, format)
File "/root/venv/lib64/python3.8/site-packages/pandas/core/tools/datetimes.py", line 465, in _convert_listlike_datetimes
result, tz_parsed = objects_to_datetime64ns(
File "/root/venv/lib64/python3.8/site-packages/pandas/core/arrays/datetimes.py", line 2090, in objects_to_datetime64ns
raise e
File "/root/venv/lib64/python3.8/site-packages/pandas/core/arrays/datetimes.py", line 2075, in objects_to_datetime64ns
result, tz_parsed = tslib.array_to_datetime(
File "pandas/_libs/tslib.pyx", line 364, in pandas._libs.tslib.array_to_datetime
File "pandas/_libs/tslib.pyx", line 586, in pandas._libs.tslib.array_to_datetime
File "pandas/_libs/tslib.pyx", line 582, in pandas._libs.tslib.array_to_datetime
File "pandas/_libs/tslib.pyx", line 537, in pandas._libs.tslib.array_to_datetime
File "pandas/_libs/tslibs/conversion.pyx", line 507, in pandas._libs.tslibs.conversion.convert_datetime_to_tsobject
File "pandas/_libs/tslibs/np_datetime.pyx", line 113, in pandas._libs.tslibs.np_datetime.check_dts_bounds
pandas._libs.tslibs.np_datetime.OutOfBoundsDatetime: Out of bounds nanosecond timestamp: 1-01-01 00:00:00
# end stack trace
Just as in Issue 16486, the query runs fine in my postgres db server. The code should not attempt to define a non-date or non-timestamp column as a timestamp column.
#### How to reproduce the bug:
1. Go to Issue 16486 and copy the info to create the table, load the data, and then create the dataset in V1.3.0.
2. Create a line chart with 'day_of_week' as the time column and group by column. Create SUM(avg_calories) as the metric.
3. Press Run
4. See error
### Environment (please complete the following information):
- superset version: 1.3.0
- python version: 3.8.6
- node.js version: none
- any feature flags active: --with-threads --reload --debugger
#### Screenshot
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org