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

streamingccl, rowexec: correctly mark eventStream as "streaming" #85866

Merged
merged 1 commit into from
Aug 10, 2022

Conversation

yuzefovich
Copy link
Member

This commit fixes an incomplete solution of
9bb5d30 which attempted to mark
eventStream generator builtin as "streaming" so that the columnarizer
on top of the projectSetProcessor would not buffer anything. As found
by Steven, the solution in that commit was incomplete since the
generators array is not populated at the time where MustBeStreaming
check is performed. This commit fixes that oversight by using
a different way of propagating the property - via the function
properties.

Release note: None

@yuzefovich yuzefovich requested review from stevendanna and a team August 9, 2022 23:18
@yuzefovich yuzefovich requested review from a team as code owners August 9, 2022 23:18
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@yuzefovich yuzefovich changed the title streamingccl, rowexec: correctly mark eventStream as a "streaming" streamingccl, rowexec: correctly mark eventStream as "streaming" Aug 9, 2022
This commit fixes an incomplete solution of
9bb5d30 which attempted to mark
`eventStream` generator builtin as "streaming" so that the columnarizer
on top of the `projectSetProcessor` would not buffer anything. As found
by Steven, the solution in that commit was incomplete since the
generators array is not populated at the time where `MustBeStreaming`
check is performed. This commit fixes that oversight by using
a different way of propagating the property - via the function
properties.

Release note: None
Copy link
Collaborator

@stevendanna stevendanna left a comment

Choose a reason for hiding this comment

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

LGTM. I've also tested that with this patch in place, I can unskip the streaming test that led us here.

@yuzefovich
Copy link
Member Author

TFTR!

bors r+

@craig
Copy link
Contributor

craig bot commented Aug 10, 2022

This PR was included in a batch that was canceled, it will be automatically retried

@craig
Copy link
Contributor

craig bot commented Aug 10, 2022

Build failed (retrying...):

@craig craig bot merged commit 0ad97e4 into cockroachdb:master Aug 10, 2022
@craig
Copy link
Contributor

craig bot commented Aug 10, 2022

Build succeeded:

@yuzefovich yuzefovich deleted the fix-streaming-func branch August 10, 2022 21:04
craig bot pushed a commit that referenced this pull request Nov 18, 2022
87532: streamingest: unskip TestTenantStreamingDeleteRange r=stevendanna a=adityamaru

#85866 seems to have stabilized this test, 5+ mins of stressing led to no failures so it seems safe to unskip.

Release note: None

Release justification: low risk, test only change

Fixes: #85630

Co-authored-by: adityamaru <adityamaru@gmail.com>
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.

3 participants