maxmustermann/minio
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
minio/docs/gateway/azure-limitations.md
Krishna Srinivas cea4cfa3a8 Implement S3 Gateway to third party cloud storage providers. (#3756) 
Currently supported backend is Azure Blob Storage.

```
export MINIO_ACCESS_KEY=azureaccountname
export MINIO_SECRET_KEY=azureaccountkey
minio gateway azure
```
2017-03-16 12:21:58 -07:00

1.1 KiB
Raw Blame History

Minio Azure Gateway Limitations

Gateway inherits the following Azure limitations:

  • Maximum Multipart part size is 100MB.
  • Maximum Multipart object size is 10000*100 MB = 1TB
  • No support for prefix based bucket policies. Only top level bucket policy is supported.
  • Gateway restart implies all the ongoing multipart uploads must be restarted. i.e clients must again start with NewMultipartUpload This is because S3 clients send metadata in NewMultipartUpload but Azure expects metadata to be set during CompleteMultipartUpload (PutBlockList in Azure terminology). We store the metadata sent by the client during NewMultipartUpload in memory so that it can be set on Azure later during CompleteMultipartUpload. When the gateway is restarted this information is lost.
  • Bucket names with "." in the bucket name is not supported.
  • Non-empty buckets get removed on a DeleteBucket() call.

Other limitations:

  • Current implementation of ListMultipartUploads is incomplete. Right now it returns if the object with name "prefix" has any uploaded parts.
  • Bucket notification not supported.