Skip to content

s3: respect partSize if size unknown - #289

Merged
GiedriusS merged 1 commit into
mainfrom
respect-partsize
Oct 9, 2026
Merged

GiedriusS merged 1 commit into
mainfrom
respect-partsize

Conversation

@GiedriusS

Copy link
Copy Markdown
Member

If the size of the upload is unknown then with the current version partSize is also ignored. This causes a problem where I am streaming results (e.g. thanos-parquet-gateway) and know that the resulting file will never be that huge to exceed the limit of part size * number of parts. Now it allocates a lot of memory conservatively to get the maximum possible object size. See
https://github.com/minio/minio-go/blob/master/docs/API.md#PutObject.md and this
https://github.com/minio/minio-go/blob/master/api-put-object-common.go#L90-L92.

Cleanup one linter message while going through this function.

@GiedriusS
GiedriusS force-pushed the respect-partsize branch 3 times, most recently from 3669d24 to a404500 Compare October 9, 2026 11:16
If the size of the upload is unknown then with the current version
partSize is also ignored. This causes a problem where I am streaming
results (e.g. thanos-parquet-gateway) and know that the resulting file
will never be that huge to exceed the limit of part size * number of
parts. Now it allocates a lot of memory conservatively to get the
maximum possible object size. See
https://github.com/minio/minio-go/blob/master/docs/API.md#PutObject.md
and this
https://github.com/minio/minio-go/blob/master/api-put-object-common.go#L90-L92.

Cleanup one linter message while going through this function.

Signed-off-by: Giedrius Statkevičius <giedrius.statkevicius@vinted.com>
@GiedriusS
GiedriusS merged commit 72d3b9f into main Oct 9, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants