When a timezone and a postive interval offset are used in a query, data is lost on the daylight savings boundary [port to 2.7] #25081

davidby-influx · 2024-06-22T01:22:18Z

Port #25080 to 2.7 branch

…25082) (#25087) This is actually the second fix for #20238 for when the time zone falls back in autumn. closes #25078 (cherry picked from commit d60741b) closes #25080 (cherry picked from commit 0c77b4c) closes #25081

…25082) (#25087) (#25089) This is actually the second fix for #20238 for when the time zone falls back in autumn. closes #25078 (cherry picked from commit d60741b) closes #25080 (cherry picked from commit 0c77b4c) closes #25081

davidby-influx added area/queries kind/bug area/2.x OSS 2.0 related issues and PRs team/edge labels Jun 22, 2024

davidby-influx self-assigned this Jun 22, 2024

Realnameisjames mentioned this issue Jun 22, 2024

db #25084

Closed

davidby-influx mentioned this issue Jun 24, 2024

fix: GROUP BY queries with offset that crosses a DST boundary fail. (#25082) (#25087) #25089

Merged

davidby-influx closed this as completed Jun 25, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

When a timezone and a postive interval offset are used in a query, data is lost on the daylight savings boundary [port to 2.7] #25081

When a timezone and a postive interval offset are used in a query, data is lost on the daylight savings boundary [port to 2.7] #25081

davidby-influx commented Jun 22, 2024

When a timezone and a postive interval offset are used in a query, data is lost on the daylight savings boundary [port to 2.7] #25081

When a timezone and a postive interval offset are used in a query, data is lost on the daylight savings boundary [port to 2.7] #25081

Comments

davidby-influx commented Jun 22, 2024