Update the CAGGS docs with the end_offset within the current bucket nuance #3991
Conversation
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
|
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-285-docs-rfc-update-caggs-docs |
erimatnor
reviewed
Apr 10, 2025
|
|
||
| In addition, materializing the most recent bucket might interfere with | ||
| [real-time aggregation][future-watermark]. | ||
| and extends to the beginning or end of time. If you set `end_offset` within the current time bucket, and [real-time aggregation][future-watermark] is disabled, the current time bucket is excluded. This is to improve performance: for time-series data that mostly contains writes that occur in the time stamp order, the time buckets that see lots of writes quickly have out-of-date aggregates. You get better performance by excluding the time buckets that are getting a lot of writes. |
Member
There was a problem hiding this comment.
FWIW: another reason is also that you cannot really refresh a partial bucket. You either compute the whole bucket or not at all.
erimatnor
approved these changes
Apr 10, 2025
billy-the-fish
approved these changes
Apr 14, 2025
Contributor
billy-the-fish
left a comment
billy-the-fish
left a comment
There was a problem hiding this comment.
I've had a go, but that sentence is still tricky.
| * `schedule_interval`: the refresh interval in minutes or hours. Defaults to | ||
| 24 hours. | ||
|
|
||
| If you set the `start_offset` or `end_offset` to `NULL`, the range is open-ended |
Contributor
There was a problem hiding this comment.
Suggested change
| If you set the `start_offset` or `end_offset` to `NULL`, the range is open-ended | |
| If you set `start_offset` or `end_offset` to `NULL`, the range is open-ended |
|
|
||
| In addition, materializing the most recent bucket might interfere with | ||
| [real-time aggregation][future-watermark]. | ||
| and extends to the beginning or end of time. If you set `end_offset` within the current time bucket, and [real-time aggregation][future-watermark] is disabled, the current time bucket is excluded. This is because the current bucket is incomplete and can't be refreshed. Excluding the current bucket also improves performance: for time-series data that mostly contains writes that occur in the time stamp order, the time buckets that see lots of writes quickly have out-of-date aggregates. You get better performance by excluding the time buckets that are getting a lot of writes. |
Contributor
There was a problem hiding this comment.
Suggested change
| and extends to the beginning or end of time. If you set `end_offset` within the current time bucket, and [real-time aggregation][future-watermark] is disabled, the current time bucket is excluded. This is because the current bucket is incomplete and can't be refreshed. Excluding the current bucket also improves performance: for time-series data that mostly contains writes that occur in the time stamp order, the time buckets that see lots of writes quickly have out-of-date aggregates. You get better performance by excluding the time buckets that are getting a lot of writes. | |
| and extends to the beginning or end of time. If you set `end_offset` within the current time bucket while [real-time aggregation][future-watermark] is disabled, the current time bucket is excluded. Incomplete time buckets cannot be refreshed, this is because the current bucket is incomplete, also time buckets that see lots of writes quickly have out-of-date aggregates. Excluding the current bucket improves performance: time-series data mostly contains writes that occur in time stamp order, you get better performance by excluding the time buckets that are getting a lot of writes. |
Co-authored-by: Iain Cox <iain@timescale.com> Signed-off-by: Anastasiia Tovpeko <114177030+atovpeko@users.noreply.github.com>
billy-the-fish
pushed a commit
that referenced
this pull request
May 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.