Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report not possible during time-shift #2

Closed
2 tasks
jakobbraun opened this issue Jan 27, 2021 · 2 comments
Closed
2 tasks

Report not possible during time-shift #2

jakobbraun opened this issue Jan 27, 2021 · 2 comments
Labels
blocked:yes Currently blocked by another ticket bug Unwanted / harmful behavior

Comments

@jakobbraun
Copy link
Contributor

jakobbraun commented Jan 27, 2021

In case your Exasol database uses a timezone with a time-shift as DBTIMEZONE, this adapter will not report the hour when the time is shifted back, since Exasol stores the statistics entries in the DBTIMEZONE and by that, the log entries are ambiguous in that hour.

Steps for Fix:

  • Change column EXA_STATISTICS table to use TIMESTAMP WITH LOCAL TIMEZONE instead of TIMESTAMP or store entries in UTC.
  • Change this adapter to use the new API
@jakobbraun jakobbraun added bug Unwanted / harmful behavior blocked:yes Currently blocked by another ticket labels Jan 27, 2021
@redcatbear
Copy link
Contributor

@jakobbraun: I don't see this happening in the core anytime soon. Please write into the user guide as known limitation and close the ticket.

@jakobbraun
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked:yes Currently blocked by another ticket bug Unwanted / harmful behavior
Projects
None yet
Development

No branches or pull requests

2 participants