sbarlock opened a new issue #6284: Timestamped data with PostgreSQL backend
URL: https://github.com/apache/incubator-superset/issues/6284
 
 
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [ x] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [ x] I have reproduced the issue with at least the latest released version 
of superset.
   - [ x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   
   ### Superset version
   0.28.1
   
   ### Expected results
   When using timestamped data from a PostgreSQL database, time series graphs 
are not working.
   Error found in logs is: 
   
   File "/usr/local/lib/python3.6/site-packages/superset/utils.py", line 360, 
in datetime_to_epoch                                                            
                                                                      
superset_server |     return (dttm - epoch_with_tz).total_seconds() * 1000
   superset_server |   File "pandas/_libs/tslibs/timestamps.pyx", line 311, in 
pandas._libs.tslibs.timestamps._Timestamp.__sub__                               
                                                                                
                         
   superset_server | TypeError: Timestamp subtraction must have the same 
timezones or no timezones
   
   This is fixed by setting utc=True in viz.py:
   
   sed -i -e 's/utc=False/utc=True/g' 
/usr/local/lib/python3.5/dist-packages/superset/viz.py
   
   Could not this be set as a default ?
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to