docs: DOC-1107: Improve blink table docs#7651
Open
margaretkennedy wants to merge 3 commits intodeephaven:mainfrom
Open
docs: DOC-1107: Improve blink table docs#7651margaretkennedy wants to merge 3 commits intodeephaven:mainfrom
margaretkennedy wants to merge 3 commits intodeephaven:mainfrom
Conversation
Contributor
elijahpetty
reviewed
Feb 4, 2026
Contributor
elijahpetty
left a comment
There was a problem hiding this comment.
Needs gifs for examples, otherwise LGTM
|
|
||
| To get around these restrictions, you can use [`removeBlink`](../table-operations/create/remove-blink.md) to opt out of special semantics. Then, you can use [`partitionBy`](../table-operations/group-and-aggregate/partitionBy.md) to get a result with constituents that will blink in and out of existence. | ||
|
|
||
| ```groovy order=null |
Contributor
There was a problem hiding this comment.
Add gif displaying results
| The following example demonstrates the difference in aggregation behavior. With the blink attribute, `sumBy` accumulates over all rows ever seen. After `removeBlink`, `sumBy` only sums rows in the current cycle. | ||
|
|
||
| ```groovy order=tNoBlink,tBlink | ||
| ```groovy ticking-table order=tBlinkSum,tNoBlinkSum |
|
|
||
| In this example: | ||
|
|
||
| - `tBlinkSum` continuously grows as it aggregates over all historical data. |
Contributor
There was a problem hiding this comment.
Suggested change
| - `tBlinkSum` continuously grows as it aggregates over all historical data. | |
| - `tBlinkSum` grows continuously as it aggregates over all historical data. |
|
|
||
| To get around these restrictions, you can use [`remove_blink`](../table-operations/create/remove-blink.md) to opt out of special semantics. Then, you can use [`partition_by`](../table-operations/group-and-aggregate/partitionBy.md) to get a result with constituents that will blink in and out of existence. | ||
|
|
||
| ```python order=null |
| The following example demonstrates the difference in aggregation behavior. With the blink attribute, `sum_by` accumulates over all rows ever seen. After `remove_blink`, `sum_by` only sums rows in the current cycle. | ||
|
|
||
| ```python order=t_no_blink,t_blink | ||
| ```python ticking-table order=t_blink_sum,t_no_blink_sum |
|
|
||
| In this example: | ||
|
|
||
| - `t_blink_sum` continuously grows as it aggregates over all historical data. |
Contributor
There was a problem hiding this comment.
Suggested change
| - `t_blink_sum` continuously grows as it aggregates over all historical data. | |
| - `t_blink_sum` grows continuously as it aggregates over all historical data. |
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
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.