Timezone offset doesn't work.

[maltitco]

The "Timezone offset" doesn't work for the postergsql database.
I am trying to display a list of records for my local time, despite setting the offset to 2 hours I still have UTC time.

I tested two ways to install the superset: using Docker and local development installation.

Edit:
I also tested this for example data that can be initiated by installing a superset.
Timezone offset setting for the flight table also does not shift time from UTC to my local.

[ericandrewmeadows]

@maltitco - which version are you running? Have you been able to test this on v0.33.0rc1?

[viveksatasiya]

I have also found same issue. I have configured time offset into data source configuration to 11(Australia/Melbourne). After configuration, still I am not able to get the data according to the time offset. I am using druid cluster.

[maltitco]

@ericandrewmeadows version from git in file superset/assets/package.json is "0.999.0dev"
@viveksatasiya I am using the postgresql database and as a workaround, I set my time zone for the user connecting to the database

[viveksatasiya]

@maltitco how to do it with the druid cluster?

[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.

[maltitco]

@viveksatasiya i don't use druid cluster.

[TheRum]

Any Update on this !

[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.

[jiade52000]

update! I have found the same issue. T.T

[poleft]

found the same issue, too.

[skymarstroy]

found the same issue, too.

[waqasakramef]

found the same issue, too.

[raowaqasakram]

Still facing the same issue.

[rusackas]

@zhaoyongjie if I recall correctly, you were just mentioning a timezone offset issue you spotted. Is that related to this bug, which incidentally our very oldest open bug report? 🤞

[manojsahukar]

Why the Hours offset doesn't support float values? I need float values for IST (+5:30)

[alex1404]

+1
why it's not working for float values

[irisjae]

A workaround is alter role <superset-role> set time zone <my-time-zone>; for the role used in the superset data connection, so that date_trunc etc used in charts are against local time.

[rusackas]

@john-bodley you have any context on this? The issue is an antique, but seemingly ever-present.

[john-bodley]

@rusackas no I don't and I'm not well educated in the PostgreSQL space.

Would someone be able to provide a concrete example (with SQL and possibly screenshots) of the exact problem? I know timezones can be tricky and I'm not overly sure how well they are supported in Superset (for context at Airbnb our data is encoded at UTC and thus we likely haven't experienced any time zone offset quirks).

To further complicate things the underlying DB-API needs to handle timezones as well as I suspect not all do. I previously added this document which highlights a slew of headaches when dealing with timezones, if that helps.