-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgres timestamp when using Include Time in table view #6763
Comments
I believe this was fixed in #6453. I checked that it hasn't made it's way into 0.29rc7, but is present in the 0.30 branch. |
I got the latest commit (a62a8d3) and tried again. It seems to have fixed the issue with columns of
|
Are you on pandas 0.24? |
Upgrading from pandas 0.23.1 to 0.24 now gives me this error:
|
Same here... |
See #6765 |
@kdorsel Have you tried on py36? I don't currently have a py37 setup, but was unable to replicate on py36. |
On py36 there are no errors, correct. Now I've started looking into the actual timestamp though. The time grain function seems to be changing the outputted times themselves. Here is an example output of tz and without tz from postgres directly. This information was inserted at 15:17:26 localtime at -05:00 offset (America/Toronto).
Here's the same output from superset grouping by ts and with the time grain checked. As can be seen, the time column. It looks like the time grain is applying the tz offset to columns with no tz, first example. And also applying the tz offset a second time to the with tz column.
|
Weird, I switched over to python 3.7.2 and can't reproduce the error. Check my
|
Yes, removing the |
Ok, on a different system WSL ubuntu 18.04 vs macOS 10.13 on py37 I also have no errors. That is with and without the UTC fix. I am using the current master branch though whereas the macOS testing was done with the latest releases. I will not be able to try the master branch on macOS for an extended period of time unfortunately. |
Ok, if you were unable to repro the py37 issue on master I think it's safe to assume it's been fixed, and removing the |
Superset version
I'm running MacOS 10.13 with python 3.7 and postgres 11
I've tried on both version each in a different venv.
0.28.1
0.29.0rc7
Expected results
To correctly scrub time and display time grouping
Actual results
When using a column of type
timestamp with timezone
I get the following error. This is the same error on both versions of superset.When using a
timestamp without time zone
I get the following. Again on both versions.Steps to reproduce
I created a dummy postgres table as follows:
The text was updated successfully, but these errors were encountered: