response.decode(buffer1, 0, 50);
            byte[] data1 = response.getData();

            // Second decode should overwrite
            response.decode(buffer2, 10, 60);
            byte[] data2 = response.getData();

            // Verify second decode overwrote first
            assertEquals(60, data2.length);
            assertEquals((byte) 0x22, data2[0]);
        }
    }

    @Nested

  {{end}}{{end}}
EXAMPLES:
  1. Start MinIO server on "/home/shared" directory.
     {{.Prompt}} {{.HelpName}} /home/shared

  2. Start single node server with 64 local drives "/mnt/data1" to "/mnt/data64".
     {{.Prompt}} {{.HelpName}} /mnt/data{1...64}

  3. Start distributed MinIO server on an 32 node setup with 32 drives each, run following command on all the nodes

      "accessResultData": {
        "properties": {
          "transformerName": {
            "type": "keyword"
          },
          "encoding": {
            "type": "keyword"
          },
          "data": {
            "type": "binary"
          }
        }
      },
      "contentLength": {
        "type": "long"
      },
      "lastModified": {
        "type": "long"
      },
      "ruleId": {

services:
  minio1:
    <<: *minio-common
    hostname: minio1
    volumes:
      - pdata1-1:/pdata1
      - pdata1-2:/pdata2

  minio2:
    <<: *minio-common
    hostname: minio2
    volumes:
      - pdata2-1:/pdata1
      - pdata2-2:/pdata2

  minio3:
    <<: *minio-common
    hostname: minio3
    volumes:
      - pdata3-1:/pdata1
      - pdata3-2:/pdata2

  minio4:
    <<: *minio-common

# using nginx reverse proxy, load balancing, you can access
# it through port 9000.
services:
  minio1:
    <<: *minio-common
    hostname: minio1
    volumes:
      - edata1-1:/edata1
      - edata1-2:/edata2
      - edata1-3:/edata3
      - edata1-4:/edata4

  nginx:
    image: nginx:1.19.2-alpine
    hostname: nginx
    volumes:
      - ./nginx-1-node.conf:/etc/nginx/nginx.conf:ro
    ports:
      - "9000:9000"

services:
  minio1:
    <<: *minio-common
    hostname: minio1
    volumes:
      - cdata1-1:/cdata1
      - cdata1-2:/cdata2

  minio2:
    <<: *minio-common
    hostname: minio2
    volumes:
      - cdata2-1:/cdata1
      - cdata2-2:/cdata2

  minio3:
    <<: *minio-common
    hostname: minio3
    volumes:
      - cdata3-1:/cdata1
      - cdata3-2:/cdata2

  minio4:
    <<: *minio-common

services:
  minio1:
    <<: *minio-common
    hostname: minio1
    volumes:
      - rdata1-1:/rdata1
      - rdata1-2:/rdata2

  minio2:
    <<: *minio-common
    hostname: minio2
    volumes:
      - rdata2-1:/rdata1
      - rdata2-2:/rdata2

  minio3:
    <<: *minio-common
    hostname: minio3
    volumes:
      - rdata3-1:/rdata1
      - rdata3-2:/rdata2

  minio4:
    <<: *minio-common

014cbdfdb","0f37d8dc-aaa3-4113-89b0-0a2f4af8362c"]],"distributionAlgo":"SIPMOD+PARITY"}} multisitea/data/disterasure/xl12/.minio.sys/tmp/5ad898e2-6621-448d-8a43-e5db08a0055c multisitea/data/disterasure/xl12/.minio.sys/tmp/.trash/.writable-check-3b45260e-10d3-49fa-93f0-af1103cccdd7.tmp multisitea/data/disterasure/xl12/.minio.sys/tmp/.trash/48d37e3b-c029-4237-bba7-316382d9c3d9/part.1 multisitea/data/disterasure/xl12/.minio.sys/config/history/38a3dbcb-a58f-4811-bf09-3bc6b7fbee05.kv/xl.meta XL2 Æ w Ä$•Ä...

# Extra Data Types { #extra-data-types }

Up to now, you have been using common data types, like:

* `int`
* `float`
* `str`
* `bool`

But you can also use more complex data types.

And you will still have the same features as seen up to now:

* Great editor support.
* Data conversion from incoming requests.
* Data conversion for response data.
* Data validation.
* Automatic annotation and documentation.

		SecretKey: "minio1234",
	}

	data := []byte(`config data`)
	edata1, err := madmin.EncryptData(cred1.String(), data)
	if err != nil {
		t.Fatal(err)
	}

	edata2, err := madmin.EncryptData(cred2.String(), data)
	if err != nil {
		t.Fatal(err)
	}

	tests := []struct {
		edata   []byte
		cred    auth.Credentials
		success bool
	}{
		{edata1, cred1, true},
		{edata2, cred2, true},