We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Steps to reproduce:
import "array" import "timezone" array.from(rows:[ {_time: 2022-03-12T00:00:00Z, _value: 10}, {_time: 2022-03-12T06:00:00Z, _value: 20}, {_time: 2022-03-12T12:00:00Z, _value: 30}, {_time: 2022-03-12T18:00:00Z, _value: 40} ]) |> aggregateWindow(every: 1d, fn:mean, location: timezone.location(name: "America/Los_Angeles"))
Expected behavior: Data are returned.
Actual behavior: Error error calling function "location" @10:52-10:98: unknown time zone America/Los_Angeles occurs.
error calling function "location" @10:52-10:98: unknown time zone America/Los_Angeles
Environment info:
Workaround is to download zoneinfo.zip from Go repo and set ZONEINFO env var. Discussed at https://community.influxdata.com/t/error-while-defining-location-parameter-for-aggregatewindow/24433.
zoneinfo.zip
ZONEINFO
The text was updated successfully, but these errors were encountered:
Thank you @alespour for putting this in the issues.
Sorry, something went wrong.
Still an issue with InfluxDB 2.4.0
Still an issue with InfluxDB 2.7.1
Having the same problem w/ InfluxDB 2.7.1 and this is a critical issue. The none existent support is unacceptable.
Same in v2.7.6 with timezone "Europe/Berlin" :(
No branches or pull requests
Steps to reproduce:
Expected behavior:
Data are returned.
Actual behavior:
Error
error calling function "location" @10:52-10:98: unknown time zone America/Los_Angeles
occurs.Environment info:
Workaround is to download
zoneinfo.zip
from Go repo and setZONEINFO
env var. Discussed at https://community.influxdata.com/t/error-while-defining-location-parameter-for-aggregatewindow/24433.The text was updated successfully, but these errors were encountered: