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

Dynamically configure spooling properties #24757

Merged
merged 3 commits into from
Jan 21, 2025
Merged

Conversation

wendigo
Copy link
Contributor

@wendigo wendigo commented Jan 21, 2025

Description

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## Clients
* Allow configuring spooling behaviour via session properties ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Jan 21, 2025
@wendigo wendigo requested review from losipiuk and dekimir January 21, 2025 13:44
@wendigo wendigo force-pushed the serafin/spooling-config branch from 0284c38 to 259c482 Compare January 21, 2025 14:09
@wendigo wendigo merged commit dafa0c6 into master Jan 21, 2025
101 of 105 checks passed
@wendigo wendigo deleted the serafin/spooling-config branch January 21, 2025 15:06
@github-actions github-actions bot added this to the 469 milestone Jan 21, 2025
@@ -160,11 +165,11 @@ public OutputSpoolingOperator(OperatorContext operatorContext, QueryDataEncoder
{
this.operatorContext = requireNonNull(operatorContext, "operatorContext is null");
this.controller = new OutputSpoolingController(
spoolingConfig.isAllowInlining(),
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't spoolingConfig now an unused parameter? If so, let's drop it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants