This message was deleted.
# generals
Slackbot
09/18/2023, 3:04 AMThis message was deleted.
r
Renato Santos
09/18/2023, 2:14 PMThe issue is that druid is losing the timezone info?
I don't really know if druid can store the time zone in the "primary key" (__time/primary indexing column)
maybe you can try to store it again in another dimension column, to retain the data as is, with the -05:00
👍 1
Renato Santos
09/18/2023, 2:17 PM2023-09-18T015426.949Z is indeed the same time as 2023-09-17T205426.949154-05:00 but in UTC
After ingestion, you can get the data back in any time zone you want
👍 1
Renato Santos
09/18/2023, 2:18 PMthe only time this could be a deal break is if you are doing daily aggregate/rollup, then I recommend you to use Hourly aggregate if you can ignore the weird timezone's
f
Forrest Holifield
09/19/2023, 12:31 AMDang, good point. I completely missed the UTC time conversion. Thanks for the help!
Forrest Holifield
09/19/2023, 12:46 AMAlso was able to just convert it at query time with the time_format function.
Forrest Holifield
09/19/2023, 12:46 AMex. (TIME_FORMAT(__time,'yyyy-MM-dd HHmmss','America/Chicago'))
r
Renato Santos
09/19/2023, 12:46 AMyou can change it by using the context parameter https://druid.apache.org/docs/latest/querying/sql-query-context/#example-using-json-api
Renato Santos
09/19/2023, 12:46 AMor the web console
f
Forrest Holifield
09/19/2023, 12:49 AMNice, thanks for that! Super helpful!