From d3180e5625817f2d8abee4d6e7f3da1642a9816f Mon Sep 17 00:00:00 2001 From: Andrew Gaul Date: Sun, 16 Apr 2017 19:31:25 -0700 Subject: [PATCH] Updated Storage backend compatibility (markdown) --- Storage-backend-compatibility.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Storage-backend-compatibility.md b/Storage-backend-compatibility.md index 46601fb..6f9b557 100644 --- a/Storage-backend-compatibility.md +++ b/Storage-backend-compatibility.md @@ -26,7 +26,6 @@ Some storage backends do not support all the features of S3: ## filesystem -* does not support listing in-progress multipart uploads * does not support object metadata on Mac OS X, see [JDK-8030048](https://bugs.openjdk.java.net/browse/JDK-8030048) * does not support object metadata using Docker and aufs, see [docker/docker#1070](https://github.com/docker/docker/issues/1070) @@ -34,7 +33,7 @@ Some storage backends do not support all the features of S3: * does not allow arbitrary list markers, partially emulated by mapping the last key to the opaque marker * does not return ETag as an MD5 hash, instead returning opaque data -* does not support listing multipart uploads +* does not support listing in-progress multipart uploads * limits multi-part uploads to 32 parts ## OpenStack Swift @@ -42,5 +41,6 @@ Some storage backends do not support all the features of S3: * does not support Content-Language headers * does not support copying objects with the If-None-Match header * does not support deleting user metadata keys, only replacing them +* does not support listing in-progress multipart uploads * does not support object-level access control * exposes multipart upload parts as regular keys \ No newline at end of file