Flush import bulks on byte size, not just doc count - #1091
Merged
Conversation
With -full-geometry a single document can carry a large polygon, so a fixed 10000 docs/bulk could exceed OpenSearch's http.max_content_length (100 MB) and fail with HTTP 413. Estimate each doc's size from its geometry point count and flush when either the count or a ~50 MB byte cap is reached. Fixes komoot#1090
lonvia
reviewed
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With -full-geometry a single document can carry a large polygon, so a fixed 10000 docs/bulk could exceed OpenSearch's http.max_content_length (100 MB) and fail with HTTP 413. Estimate each doc's size from its geometry point count and flush when either the count or a ~50 MB byte cap is reached.
Fixes #1090