Fix storage uploads: use preferred chunk size #1743
Merged
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.
Description
Problem:
We were not hitting this before because for nuclia-hosted nucliadb, it is NUA processing who pushes the files to the bucket already in the right key.
However, for NucliaDB Onprem, processed files need to be downloaded from NUA processing api and uploaded to NucliaDB's blob storage.
So far we had never hit this issue because we were using always PG and local file backends, which have no restrictions on chunk sizes.
Right now, when uploading to the GCS bucket we get these errors:
This is something that I had fixed for the export/import, but it is hitting us now OnPrem when ingesting messages from NUA.
How was this PR tested?
Unit tests & local tests