- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 19 for DELETE (0.2 sec)
-
docs/bucket/lifecycle/README.md
} ] } ``` ### 3.3 Automatic removal of delete markers with no other versions When an object has only one version as a delete marker, the latter can be automatically removed after a certain number of days using the following configuration: ``` { "Rules": [ { "ID": "Removing all delete markers", "Expiration": { "DeleteMarker": true
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sat Aug 26 07:33:25 GMT 2023 - 9K bytes - Viewed (1) -
docs/bucket/versioning/README.md
To permanently delete an object you need to specify the version you want to delete, only the user with appropriate permissions can permanently delete a version. As shown below DELETE request called with a specific version id permanently deletes an object from a bucket. Delete marker is not added for DELETE requests with version id.
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu May 04 21:43:52 GMT 2023 - 11.9K bytes - Viewed (1) -
docs/security/README.md
- Seal/Unmount one/some master keys. That will lock all SSE-S3 encrypted objects protected by these master keys. All these objects can not be decrypted as long as the key(s) are sealed.
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 13.8K bytes - Viewed (0) -
README.md
## Overview * Full-Featured ORM * Associations (Has One, Has Many, Belongs To, Many To Many, Polymorphism, Single-table inheritance) * Hooks (Before/After Create/Save/Update/Delete/Find) * Eager loading with `Preload`, `Joins` * Transactions, Nested Transactions, Save Point, RollbackTo to Saved Point * Context, Prepared Statement Mode, DryRun Mode * Batch Insert, FindInBatches, Find To Map
Plain Text - Registered: Sun Apr 28 09:35:09 GMT 2024 - Last Modified: Tue Nov 07 02:20:06 GMT 2023 - 1.8K bytes - Viewed (0) -
docs/bucket/replication/README.md
``` mc replicate edit alias/bucket --id xyz.id --replicate "delete,delete-marker" ``` To re-enable replica metadata modification syncing, ``` mc replicate edit alias/bucket --id xyz.id --replicate "delete,delete-marker,replica-metadata-sync" ``` ## MinIO Extension ### Replicating Deletes
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Tue Jan 24 23:46:33 GMT 2023 - 18.2K bytes - Viewed (0) -
docs/multi-user/admin/README.md
Once the user is successfully created you can now apply the `userManage` policy for this user. ``` mc admin policy attach myminio userManager --user=admin1 ``` This admin user will then be allowed to perform create/delete user operations via `mc admin user` ### 3. Configure `mc` and create another user user1 with attached policy user1policy ``` mc alias set myminio-admin1 http://localhost:9000 admin1 admin123 --api s3v4
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Tue Mar 21 06:38:06 GMT 2023 - 4.5K bytes - Viewed (0) -
manifests/charts/ztunnel/README.md
## Installing the Chart To install the chart: ```console helm install ztunnel istio/ztunnel ``` ## Uninstalling the Chart To uninstall/delete the chart: ```console helm delete ztunnel ``` ## Configuration To view support configuration options and documentation, run: ```console helm show values istio/ztunnel ``` ### Profiles
Plain Text - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0) -
cni/README.md
- `istio-cni-config` configmap with CNI plugin config to add to CNI plugin chained config - creates service-account `istio-cni` with `ClusterRoleBinding` to allow gets on pods' info and delete/modifications for recovery. - `install-cni` container - copies `istio-cni` and `istio-iptables` to `/opt/cni/bin` - creates kubeconfig for the service account the pod runs under
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Feb 28 17:29:38 GMT 2024 - 12.1K bytes - Viewed (0) -
docs/bucket/notifications/README.md
| `s3:ObjectCreated:Put` | `s3:ObjectCreated:CompleteMultipartUpload` | `s3:ObjectAccessed:Head` | | `s3:ObjectCreated:Post` | `s3:ObjectRemoved:Delete` | `s3:ObjectRemoved:DeleteMarkerCreated` | | `s3:ObjectCreated:Copy` | `s3:ObjectAccessed:Get` | |
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
docs/bigdata/README.md
workloads rely on HDFS atomic rename functionality to complete writing data to the datastore. Object storage operations are atomic by nature and they do not require/implement rename API. The default S3A committer emulates renames through copy and delete APIs. This interaction pattern causes significant loss of performance because of the write amplification. _Netflix_, for example, developed two new staging committers - the Directory staging committer and the Partitioned staging committer - to take...
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 14.7K bytes - Viewed (0)