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

Lazily create buffers used in FileSystemExchangeSink #13855

Merged
merged 1 commit into from
Aug 30, 2022

Conversation

linzebing
Copy link
Member

Description

Is this change a fix, improvement, new feature, refactoring, or other?

Improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

trino-exchange-filesystem

How would you describe this change to a non-technical end user or system administrator?

This reduces the memory usage of fault tolerant execution

Related issues, pull requests, and links

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

() No release notes entries required.
(x) Release notes entries required with the following suggested text:

# Section
* Improved memory-consumption of fault-tolerant execution.

@cla-bot cla-bot bot added the cla-signed label Aug 26, 2022
@linzebing linzebing requested review from losipiuk and arhimondr and removed request for losipiuk August 26, 2022 00:02
@losipiuk
Copy link
Member

image
relevant?

@linzebing linzebing force-pushed the lazily-create-sink-buffers branch from 6c5e293 to 4f6fa5a Compare August 26, 2022 17:45
@linzebing
Copy link
Member Author

@losipiuk doesn't seem so

@losipiuk losipiuk merged commit 21c2bc1 into trinodb:master Aug 30, 2022
@github-actions github-actions bot added this to the 395 milestone Aug 30, 2022
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