feat: make stream_unsafe_cache_size
a session variable
#22691
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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Right now, it is a global configuration variable. This PR makes a session variable.
first_value
andlast_value
when the input is append-only #22293. Under append-only settings, some aggregation functions only need to store and cache 1 element, but right now we keep 10 elements in cache while storing all the elements.set stream_extreme_cache_size to 1
does not make sense for other queries.Checklist
Documentation
Release note