You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be another way to resolve #318.
Prerequisites:
grafana 8.4.4(fcfb01faeb)
plugin vertamedia-clickhouse-datasource @ 2.5.2
What happened:
in table view, datetime is interpreted as of browser's timezone.
Steps to reproduce:
set system timezone as UTC+3;
create table with datetime:
(
dt DATETIME64,
value Int64
)
ENGINE = MergeTree()
ORDER BY (dt)
SETTINGS index_granularity = 8192;
insert values(60 time points starting 2022-09-28 12:00:00 UTC - 12:00:59 UTC):
insert into test(dt, value)
with timeseries_cte as (
select toDateTime(number) as dt,
mod(number, 10) as value
from numbers(1664366400, 60)
)
select dt, value from timeseries_cte;
add a panel with clickhouse datasource and the following query:
SELECT
dt,
--toTimezone(dt, 'UTC'),
avg(value)
FROM market_risk.opst1228
GROUP BY dt
ORDER BY dt
select table view;
Expected behaviour: datetimes are interpreted as UTC and shown unmodified
Actual behaviour: datetimes were interpreted as browser's timezone(UTC+3) and modified so it's 9:00:00, 9:00:01 etc
The similar issue #318 was closed as wontfix since there was no way to interpret server timezone from Clickhouse HTTP response. It seems it's possible now via x-clickhouse-timezone header. x-clickhouse-timezone: UTC
The text was updated successfully, but these errors were encountered:
This might be another way to resolve #318.
Prerequisites:
grafana
8.4.4(fcfb01faeb)
plugin
vertamedia-clickhouse-datasource @ 2.5.2
What happened:
in table view, datetime is interpreted as of browser's timezone.
Steps to reproduce:
Expected behaviour: datetimes are interpreted as UTC and shown unmodified
Actual behaviour: datetimes were interpreted as browser's timezone(UTC+3) and modified so it's 9:00:00, 9:00:01 etc
The similar issue #318 was closed as
wontfix
since there was no way to interpret server timezone from Clickhouse HTTP response. It seems it's possible now viax-clickhouse-timezone
header.x-clickhouse-timezone: UTC
The text was updated successfully, but these errors were encountered: