- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for zeros (0.2 sec)
-
docs/bucket/lifecycle/README.md
}, "NoncurrentVersionExpiration": { "NewerNoncurrentVersions": 5 } } ] } ``` Note: This rule has an implicit zero NoncurrentDays, which makes the expiry of those 'extra' noncurrent versions immediate. #### 3.2.b Automatic removal of all versions (MinIO only extension)
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Aug 26 07:33:25 GMT 2023 - 9K bytes - Viewed (1) -
docs/bucket/versioning/README.md
versioning-enabled bucket, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object versions in the versioning-enabled bucket. (A version-enabled bucket maintains one current and zero or more noncurrent object versions.) Versioning must be explicitly enabled on a bucket, versioning is not enabled by default. Object locking enabled buckets have versioning enabled automatically. Enabling and suspending versioning is done at...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu May 04 21:43:52 GMT 2023 - 11.9K bytes - Viewed (1) -
README.md
## Upgrading MinIO Upgrades require zero downtime in MinIO, all upgrades are non-disruptive, all transactions on MinIO are atomic. So upgrading all the servers simultaneously is the recommended way to upgrade MinIO.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 17:51:34 GMT 2024 - 18.7K bytes - Viewed (0)