How to change timezone for TP to timestamp data in to local timezone

98 views
Skip to first unread message

Mixa

unread,
Jan 17, 2024, 9:52:30 AM1/17/24
to Data Intellect kdb+/TorQ
Hello all,
I've experienced  a  problem making TP to store timestamps in my local time (GMT+3). In accordance with documentation I changed default.q in this way:

// timezone functions
\d .tz
default:`$"Europe/Istanbul"   // default local timezone

\d .eodtime
rolltimeoffset:0D00:00:00.000000000;    // offset from default midnight roll
datatimezone:`$"Europe/Istanbul";         // timezone for TP to timestamp data in
rolltimezone:`$"Europe/Istanbul";         // timezone to perform rollover in

All processes in the stack are started with `-localtime`.
Requested data from the gateway shows timestamps in GMT+0 time. Hence timestamp in logs are in local time. Also I tried to set datatimezone to different values (EST, GMT+3, etc) to test any effect but with no success.

My setup is the same:  Windows 2019 Server and recent stack.

Please help me in this regard.

Mixa

Jamie Peters

unread,
Jan 19, 2024, 6:41:48 AM1/19/24
to Data Intellect kdb+/TorQ
Hi Mixa, 

If you haven't solved this yet, I think the issue is that the appconfig settings for the segmentedtickerplant are overriding this, so rather than changing these in default.q you'll want to change them in /appconfig/settings/segmentedtickerplant.q, hope this helps.

Jamie

Mixa

unread,
Jan 22, 2024, 3:09:29 AM1/22/24
to Data Intellect kdb+/TorQ
Jamie,
Thanks a lot for patience. You are right. I modified the wrong config. 
Hope my questions and your answers will save a lot of time for other new users of TORQ.
Mixa
Reply all
Reply to author
Forward
0 new messages