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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
my elasticSearch sink dataset parameter is setted by %Y-%m-%d ,however vector internal %Y, %m, %d is derived from timestamp field which timezone is always utc, i wanna to set %Y-%m-%d using "Asia/Shang" timezone, but i found i can't without using either set global timestamp key option. or adding extra column which value timezone is setted from format_timestamp
problem:
vector/vrl now is hardcode timezone value is utc, which result in parse_timestamp that default timezone is utc and could not be change , format_timestamp can set timezone, but return value type is string not timestamp ; if parse_timestamp could support timezone ,that's would be great
best wishes
Attempted Solutions
No response
Proposal
No response
References
No response
Version
No response
The text was updated successfully, but these errors were encountered:
A note for the community
Use Cases
my elasticSearch sink dataset parameter is setted by %Y-%m-%d ,however vector internal %Y, %m, %d is derived from timestamp field which timezone is always utc, i wanna to set %Y-%m-%d using "Asia/Shang" timezone, but i found i can't without using either set
global timestamp key option.
or adding extra column which value timezone is setted from format_timestampproblem:
vector/vrl now is hardcode timezone value is utc, which result in parse_timestamp that default timezone is utc and could not be change , format_timestamp can set timezone, but return value type is string not timestamp ; if parse_timestamp could support timezone ,that's would be great
best wishes
Attempted Solutions
No response
Proposal
No response
References
No response
Version
No response
The text was updated successfully, but these errors were encountered: