MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2024-12-26 23:25:54 -05:00
Code Issues Packages Projects Releases Wiki Activity
3c836b5f34
minio/docs/gateway/azure-limitations.md
Krishnan Parthasarathi f7ae3be586 Removing 100MB part and 1TB limitation (#4939) 
With https://github.com/minio/minio/pull/4869 maximum size of a single
multipart upload part in not restricted to 100MB. 1TB maximum object
size limitation is no longer applicable too.
2017-09-20 09:48:48 -07:00

1007 B
Raw Blame History

Minio Azure Gateway Limitations

Gateway inherits the following Azure limitations:

  • 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.