Versions Compared

Old Version 13

changes.mady.by.user Kyle Miller

Saved on

compared with

New Version Current

changes.mady.by.user Kyle Miller

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Corrects an issue with S3 multipart writes on storage clusters where parallel uploads are not performed. This resulted in listing errors when using Cyberduck version 5.0. (5.1.0: CLOUD-2398)

  • Case-insensitive metadata searching within Swarm 9 storage cluster is now compatible with the S3 protocol front-end once you complete the migration to Elasticsearch 2.3. (SWAR-5283, SWAR-6317)

  • Long metadata field names are truncated in collections display in order to improve readability. (5.1.0: CLOUD-1691)

  • Help links for both 'Documentation' and 'Online Support' in the Content Portal are now customizable through edits to the file _admin/portal/customLinks.json. (5.1.0: CLOUD-1987)

  • Fixed an issue that caused a failure when using SCSP APPEND through the Gateway. (5.1.2: CLOUD-2629)

  • Fixed an issue in which the loss of one Elasticsearch node in a multi-node Elasticsearch cluster resulted in failure to perform queries and perform S3 listings. (5.1.2: CLOUD-2412)

  • Fixed an issue that threw an error and prevented an object delete when the context disallowed versioning. (5.1.1: CLOUD-2611)

  • Improved the reliability of S3 multipart upload completion. (5.1.2: CLOUD-2414)

  • Improved the handling of Swarm errors during S3 multipart upload completion. (5.1.3: CLOUD-2633)

  • Fixed: Using the utility 's3cmd' v1.6.1, attempts to perform 's3cmd mv' from one filename to another and/or one bucket to another failed for large (100+ MB) files. (5.1.3: CLOUD-2659)

  • Fixed: A change in Swarm 9.1.0 caused S3 header "x-amz-delete-marker: true" to no longer be sent in response to a HEAD of a deleted object, although the header was still returned on GET. (5.1.3: CLOUD-1041)

  • Fixed: Gateway 5.0.0 - 5.1.2 S3 listings did not include any ETag for objects uploaded via SCSP parallel write or S3 multipart APIs because they had no Content-MD5. The missing XML key broke clients such as s3cmd. Gateway now includes the same generated (non-MD5) ETag in listings as is returned on a GET of the object. Gateway and Swarm Storage now generate a "composite MD5" of the parts, similar to AWS S3, and Gateway uses that as the object's ETag in S3 response headers and listings. (5.1.3: CLOUD-1496)

  • Fixed: Using V4 signatures with some S3 clients (such as rclone) may receive a 403 signature mismatch error caused by the request header "Content-type" containing a lowercase "charset". (5.1.3: CLOUD-2664)

  • Fixed: When using the S3 list multipart uploads operation, if there are multiple simultaneous uploads in progress for a single object, only one of the uploads is included in the listing. (5.1.3: CLOUD-2333)

...