feat: fix DefaultMaxPayloadSize from 2GB to 64GB #307
Merged
Conversation
This file contains 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
unclezoro
approved these changes
Jul 4, 2023
This was referenced Jul 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Due to the addition of resumable upload and resumable download functionalities(bnb-chain/greenfield-storage-provider#480 & bnb-chain/greenfield-go-sdk#91 ), we now allow uploading larger files to Greenfield. Therefore, we have increased the value of DefaultMaxPayloadSize from 2GB to 64 GB.
Rationale
This configuration change allows users to upload files with a maximum size of 64GB to Greenfield. The DefaultMaxPayloadSize parameter defines the maximum payload size that can be handled by the system during file uploads.
Example
NA
Changes
NA