Skip to content

docs(object): update mpu cli doc - #6986

Open
SamyOubouaziz wants to merge 3 commits into
mainfrom
MTA-7556
Open

SamyOubouaziz wants to merge 3 commits into
mainfrom
MTA-7556

Conversation

@SamyOubouaziz

Copy link
Copy Markdown
Collaborator

Your checklist for this pull request

Description

Please describe what you added or changed.

@SamyOubouaziz
SamyOubouaziz requested a review from a team as a code owner October 12, 2026 15:24
@SamyOubouaziz SamyOubouaziz added the status: doc review Waiting for doc team review label Oct 12, 2026
@SamyOubouaziz SamyOubouaziz self-assigned this Oct 12, 2026
@SamyOubouaziz SamyOubouaziz added do not review yet please wait before reviewing its not ready yet and removed status: doc review Waiting for doc team review labels Oct 12, 2026
@SamyOubouaziz SamyOubouaziz changed the title docs(object): update pmu cli doc docs(object): update mpu cli doc Oct 13, 2026
@SamyOubouaziz SamyOubouaziz added status: doc review Waiting for doc team review and removed do not review yet please wait before reviewing its not ready yet labels Oct 13, 2026
Multipart uploads allow you to upload a single object as a set of independent parts. Each part is a contiguous portion of the object's data. You can upload parts in parallel and in any order, and retry a failed part without restarting the whole upload. Once all parts are uploaded, Object Storage assembles them into a single object that you can access like any other object in the bucket.

Multipart uploads allow you to upload large files to the Object Storage platform by dividing them into multiple fragments to improve throughput and recover quickly in case of network interruption.
We recommend using multipart uploads for objects larger than 50 MB. Multipart uploads are mandatory for objects larger than 5 GB, as a single `PUT` request cannot exceed this size.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We recommend using multipart uploads for objects larger than 50 MB. Multipart uploads are mandatory for objects larger than 5 GB, as a single `PUT` request cannot exceed this size.
Scaleway recommends using multipart uploads for objects larger than 50 MB. Multipart uploads are mandatory for objects larger than 5 GB, as a single `PUT` request cannot exceed this size.

validation: 2025-07-30
posted: 2019-04-19
validation: 2026-10-12
posted: 2019-0

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
posted: 2019-0
posted: 2019-04-19

---
import Requirements from '@macros/iam/requirements.mdx'

Multipart uploads allow you to upload a single object as a set of independent parts. Each part is a contiguous portion of the object's data. You can upload parts in parallel and in any order, and retry a failed part without restarting the whole upload. Once all parts are uploaded, Object Storage assembles them into a single object that you can access like any other object in the bucket.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Multipart uploads allow you to upload a single object as a set of independent parts. Each part is a contiguous portion of the object's data. You can upload parts in parallel and in any order, and retry a failed part without restarting the whole upload. Once all parts are uploaded, Object Storage assembles them into a single object that you can access like any other object in the bucket.
Multipart uploads let you upload a single object as a set of independent parts. Each part is a contiguous portion of the object data. You can upload parts in parallel and in any order, and retry a failed part without restarting the whole upload. Once all parts are uploaded, Object Storage assembles them into a single object that you can access like any other object in the bucket.


If you upload a part using a part number that already exists, the new part overwrites the previous one.

Object Storage stores the uploaded parts until you complete or abort the upload, and bills them as regular storage. Incomplete multipart uploads that you do not abort remain billed indefinitely. Refer to [Abort a multipart upload](#abort-a-multipart-upload) for more information.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Object Storage stores the uploaded parts until you complete or abort the upload, and bills them as regular storage. Incomplete multipart uploads that you do not abort remain billed indefinitely. Refer to [Abort a multipart upload](#abort-a-multipart-upload) for more information.
Object Storage stores the uploaded parts until you complete or abort the upload, and bills them as regular storage. Incomplete multipart uploads that you do not abort remain billed indefinitely. See [Abort a multipart upload](#abort-a-multipart-upload) for more information.

- 5 MB to 5 GB per part (except for the last one)
- Each object stores up to 5 TB

| Specification | Limit |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Est-ce qu'une definition list ne serait pas mieux ? 🤔

```

## Completing a multipart upload
An output similar to the following displays:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
An output similar to the following displays:
An output similar to the following appears:

```

This command lists in-progress multipart uploads. An in-progress multipart upload is an active multipart upload request that is still ongoing and has not yet been completed or aborted.
An output similar to the following displays:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
An output similar to the following displays:
An output similar to the following appears:

---
import Requirements from '@macros/iam/requirements.mdx'

Multipart uploads allow you to upload a single object as a set of independent parts. Each part is a contiguous portion of the object's data. You can upload parts in parallel and in any order, and retry a failed part without restarting the whole upload. Once all parts are uploaded, Object Storage assembles them into a single object that you can access like any other object in the bucket.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Multipart uploads allow you to upload a single object as a set of independent parts. Each part is a contiguous portion of the object's data. You can upload parts in parallel and in any order, and retry a failed part without restarting the whole upload. Once all parts are uploaded, Object Storage assembles them into a single object that you can access like any other object in the bucket.
Multipart uploads allow you to upload a single object as a set of independent parts. Each part is a contiguous portion of the object's data. You can upload parts in parallel and in any order, and retry a failed part without restarting the whole upload. Once all parts are uploaded, Object Storage assembles them into a single object, which you can access like any other object in the bucket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: doc review Waiting for doc team review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants