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

Block upload: include converted timestamp in the error message #7538

Merged
merged 3 commits into from
Mar 5, 2024

Conversation

pstibrany
Copy link
Member

What this PR does

When user tries to upload block with timestamps in microseconds instead of milliseconds, such timestamps are converted to very distant future dates. By including converted dates in the error message, we make this more clear.

(We have seen multiple support cases about this. Most recently #7533).

Checklist

  • Tests updated.
  • [na] Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • [na] about-versioning.md updated with experimental features.

Signed-off-by: Peter Štibraný <pstibrany@gmail.com>
@pstibrany pstibrany requested a review from a team as a code owner March 5, 2024 09:07
Signed-off-by: Peter Štibraný <pstibrany@gmail.com>
Copy link
Contributor

@aknuds1 aknuds1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good, but I think you have a copy pasta mistake in the test case name.

pkg/compactor/block_upload_test.go Outdated Show resolved Hide resolved
Signed-off-by: Peter Štibraný <pstibrany@gmail.com>
@pstibrany pstibrany enabled auto-merge (squash) March 5, 2024 09:25
@pstibrany pstibrany merged commit e7530be into main Mar 5, 2024
29 checks passed
@pstibrany pstibrany deleted the include-converted-timestamps-in-the-message branch March 5, 2024 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants