-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix(gcp_cloud_storage sink): apply timezone to key_prefix strftime #25541
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
Open
xfocus3
wants to merge
1
commit into
vectordotdev:master
Choose a base branch
from
xfocus3:fix/gcs-key-prefix-timezone-25090
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| The `gcp_cloud_storage` sink now applies the configured `timezone` option (or the global `timezone`) to `strftime` specifiers in `key_prefix`, matching the behavior of the `aws_s3` sink. Previously, date-based partitioning in `key_prefix` (for example `key_prefix = "%Y%m%d/"`) was always rendered in UTC and ignored the `timezone` setting, so object paths could land in the wrong dated directory around the UTC day boundary. | ||
|
|
||
| authors: xfocus3 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
timezoneis a named zone with daylight saving time, this converts it once withtimezone_to_offset, which freezes the offset based onUtc::now()at sink build time beforeTemplateformats each event timestamp. In a sink configured withAmerica/Los_Angeles, if Vector starts during PDT (-07) but renders a winter event such as2026-12-01T07:30:00Z(still Nov 30 in PST -08), the key prefix is formatted using -07 and lands under Dec 1 instead of Nov 30. The template needs the named timezone, or an offset computed from the event timestamp, rather than a build-time fixed offset.Useful? React with 👍 / 👎.