hosswald opened a new issue, #21149:
URL: https://github.com/apache/superset/issues/21149

   #### How to reproduce the bug
   
   * Have a Druid Database with UTC timestamps in __time column
   * Connect it to Superset
   ** Add Engine Parameters: {"context":{"sqlTimeZone":"Europe/Berlin"}}
   Two tests:
   * Query __time column in SQL lab
   * Create a table chart with only the __time column
   ** Format with something like %Y-%m-%d %H:%M:%S
   
   ### Expected results
   Formatted timestamps should be in the timezone configured via 
context.sqlTimeZone
   
   ### Actual results
   SQLLab:
   
![image](https://user-images.githubusercontent.com/32925139/185933293-83dbc186-848b-4a83-a8e3-95de076bf8c9.png)
   
   Chart:
   
![image](https://user-images.githubusercontent.com/32925139/185933375-55ca4976-c852-4684-9401-4d96e0099486.png)
   
   ### Environment
   
   - browser type and version: Chrome 104.0.5112.82
   - superset version: 2.0.0 via Helm Chart 0.7.1
   - druid version: 0.23.0
   
   ### Checklist
   
   Make sure to follow these steps 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.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to