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
Describe the bug
Many tests quries for DPL have incorrect or missing timezone information. Current implementation of default timestamps means that the system default timezone is used. This can cause variance in test results between timezones.
To avoid this all dpl queries with timestamps should have zone information included!
earliest=2020-01-01T00:00:00 should be earliest=2020-01-01T00:00:00Z with Z for UTC.
earliest=2020-01-01T00:00:00z should be earliest=2020-01-01T00:00:00Z with upper case Z for proper format.
same applies for latest.
UTC is preferred for clarity.
Expected behavior
Tests should always have same results even when system timezone is changed.
How to reproduce
For direct result write a dpl test query or modify one with timestamps and inspect the ctx.getSparkQuery(). It will have different results if system default timezone is changed. query part where epoch is visible from_unixtime(1611619200, yyyy-MM-dd HH:mm:ss)
Software version
8.4.2
Additional context
Note that most of the test cases work even with small variance in the timezones.
$ grep -rlE '(earliest|latest)' . check for files with timestamps in src/test
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Many tests quries for DPL have incorrect or missing timezone information. Current implementation of default timestamps means that the system default timezone is used. This can cause variance in test results between timezones.
To avoid this all dpl queries with timestamps should have zone information included!
earliest=2020-01-01T00:00:00
should beearliest=2020-01-01T00:00:00Z
withZ
for UTC.earliest=2020-01-01T00:00:00z
should beearliest=2020-01-01T00:00:00Z
with upper caseZ
for proper format.same applies for latest.
UTC is preferred for clarity.
Expected behavior
Tests should always have same results even when system timezone is changed.
How to reproduce
For direct result write a dpl test query or modify one with timestamps and inspect the
ctx.getSparkQuery()
. It will have different results if system default timezone is changed. query part where epoch is visiblefrom_unixtime(1611619200, yyyy-MM-dd HH:mm:ss)
Software version
8.4.2
Additional context
Note that most of the test cases work even with small variance in the timezones.
$ grep -rlE '(earliest|latest)' .
check for files with timestamps insrc/test
The text was updated successfully, but these errors were encountered: