fix(http): avoid running out of memory when importing partitioned table over REST API #3638
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.
Fixes #3480
By default, the POST
/imp
REST API endpoint doesn't issue intermediate commits. This PR makes sure that we initializemaxUncommittedRows
ando3MaxLag
parameters of theCairoTextWriter
with the table's defaults, so thatwriter.ic()
calls are made during the import. As a result, the O3 memory won't be unboundedly growing when importing O3 data and chances to run OOM become much smaller.Also improves timestamp unit description in
Sender
's Javadoc