-
Notifications
You must be signed in to change notification settings - Fork 0
fix(clickhouse): key event projections tenant-first on an hourly bucket #34
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
Merged
+483
−29
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f0e86a8
fix(clickhouse): key event projections tenant-first on an hourly bucket
lohanidamodar 9f48dd0
refactor(clickhouse): scope the projection reshape to events only
lohanidamodar 9c4f491
chore(clickhouse): cut the projection comments back to the non-obviou…
lohanidamodar 89e7bb3
test(clickhouse): cover 1w and 1M bucket composition
lohanidamodar 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
Oops, something went wrong.
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.
Good catch on the coverage gap — added in 89e7bb3, which turns the day-interval test into a provider over 1d/1w/1M so each asserts both projection use and parity against a base-table scan.
On correctness the composition was already sound:
toStartOfInterval(toStartOfHour(t,'UTC'), INTERVAL X)equalstoStartOfInterval(t, INTERVAL X)with zero mismatches across 5M timestamps spanning ~5 years, for 1h/1d/1w/1M. Week and month boundaries are whole numbers of hours, so hour truncation nests inside them. But the suite was proving that only for 1d, so the guard was worth having.