Search before asking
Version
c91688b
Describe the bug and provide the minimal reproduce step
The core issue lies in org.apache.iotdb.db.utils.datetimeutils.DateTimeUtils.toZoneOffset(ZoneId zoneId). This method calculates the timezone offset using Instant.now(). In regions that observe Daylight Saving Time (DST), such as Europe/Warsaw, the offset is not constant throughout the year (+1 in winter, +2 in summer).
timezone: Europe/Warsaw
INSERT INTO root.test.d1(time, s1) VALUES(2024-01-01T00:00:00, 1);
SELECT s1 FROM root.test.d1;
What did you expect to see?
2024-01-01T00:00:00+01:00
What did you see instead?
2023-12-31T23:00:00.000+01:00
Anything else?
No response
Are you willing to submit a PR?
Search before asking
Version
c91688b
Describe the bug and provide the minimal reproduce step
The core issue lies in org.apache.iotdb.db.utils.datetimeutils.DateTimeUtils.toZoneOffset(ZoneId zoneId). This method calculates the timezone offset using Instant.now(). In regions that observe Daylight Saving Time (DST), such as Europe/Warsaw, the offset is not constant throughout the year (+1 in winter, +2 in summer).
timezone: Europe/Warsaw
INSERT INTO root.test.d1(time, s1) VALUES(2024-01-01T00:00:00, 1);
SELECT s1 FROM root.test.d1;
What did you expect to see?
2024-01-01T00:00:00+01:00
What did you see instead?
2023-12-31T23:00:00.000+01:00
Anything else?
No response
Are you willing to submit a PR?