Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for require (0.15 sec)

  1. cni/README.md

    ## Privileges required
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri May 03 19:29:42 GMT 2024
    - 12.3K bytes
    - Viewed (0)
  2. 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)
  3. docs/bigdata/README.md

    workloads typically interact with object stores in the same way they do with HDFS. These 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...
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Sep 29 04:28:45 GMT 2022
    - 14.7K bytes
    - Viewed (0)
  4. operator/README.md

    To override a setting that includes dots, escape them with a backslash (\).  Your shell may require enclosing quotes.
    
    ``` bash
    istioctl manifest generate --set "values.sidecarInjectorWebhook.injectedAnnotations.container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy=runtime/default"
    ```
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sun Sep 17 08:27:52 GMT 2023
    - 17.5K bytes
    - Viewed (0)
  5. helm/minio/README.md

    ```bash
    helm install --set existingSecret=my-minio-secret minio/minio
    ```
    
    The following fields are expected in the secret:
    
    | .data.\<key\> in Secret | Corresponding variable | Description    | Required |
    |:------------------------|:-----------------------|:---------------|:---------|
    | `rootUser`              | `rootUser`             | Root user.     | yes      |
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Wed Jan 24 07:27:57 GMT 2024
    - 10.9K bytes
    - Viewed (0)
  6. docs/bucket/replication/README.md

    The user setting up replication needs *s3:GetReplicationConfiguration* and *s3:GetBucketVersioning* permission on the source cluster. We do not recommend running root credentials/super admin with replication, instead create a dedicated user. The access credentials used at the destination requires *s3:ReplicateObject* permission.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Tue Jan 24 23:46:33 GMT 2023
    - 18.2K bytes
    - Viewed (0)
  7. README.md

        * As the `q` parameter is declared with `= None`, it is optional.
        * Without the `None` it would be required (as is the body in the case with `PUT`).
    * For `PUT` requests to `/items/{item_id}`, Read the body as JSON:
        * Check that it has a required attribute `name` that should be a `str`.
        * Check that it has a required attribute `price` that has to be a `float`.
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 22.6K bytes
    - Viewed (0)
Back to top