minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-30 07:03:26 +03:00
Code Activity

Clarify the effect of a write operation on versioning (#1468)

Browse Source 
All write operations, mutation or not, result in a new version of that
object with a unique version ID.
This commit is contained in:
Allan Roger Reid
2025-05-27 08:10:18 -07:00
committed by GitHub
parent 50dc114036
commit 71b42c32da
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
source/administration/object-management/object-versioning.rst
View File

@ -25,7 +25,7 @@ Write operations which would normally overwrite an existing object instead resul
MinIO versioning protects from unintended overwrites and deletions while providing support for "undoing" a write operation. MinIO versioning protects from unintended overwrites and deletions while providing support for "undoing" a write operation.
Bucket versioning is a prerequisite for configuring :ref:`object locking and retention rules <minio-object-locking>`. Bucket versioning is a prerequisite for configuring :ref:`object locking and retention rules <minio-object-locking>`.
For versioned buckets, a write operation that mutates an object results in a new version of that object with a unique version ID. For versioned buckets, a write operation results in a new version of that object with a unique version ID.
MinIO marks the "latest" version of the object that clients retrieve by default. MinIO marks the "latest" version of the object that clients retrieve by default.
Clients can then explicitly choose to list, retrieve, or remove a specific object version. Clients can then explicitly choose to list, retrieve, or remove a specific object version.