Versions Compared

Old Version 6

changes.mady.by.user Jamshid Afshar

Saved on

compared with

New Version 7

changes.mady.by.user Bala Harish A(AC)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

Changes

  • Improved S3 listing performance when no prefix is specified. (CLOUD-3788)

  • Buckets that contain only version delete markers cannot be deleted, to match AWS' behavior. (CLOUD-3797)

  • Hybrid Cloud copies to S3 now preserve custom metadata. (CLOUD-3799)

Upgrade Impacts

See Upgrading Gateway, to upgrade from a version of Gateway 6. See Upgrading from Gateway 5.x, if migrating from Elasticsearch 2.3.3 and Gateway 5.

...

Insert excerpt
Content Gateway 7.0 Release
Content Gateway 7.0 Release
nopaneltrue

See See Content Gateway 6.4 Release for impacts from prior releases.

Watch Items and Issues

These are known operational limitations that exist for Gateway.

  • When using the default RHEL/CentOS configuration of IPTABLES, traffic to the Gateway will be blocked unless action is taken to disable IPTABLES or to enable inbound traffic to the front-end protocol port(s).

  • Gateway is not compatible with Linux PAM modules that depend upon interactive validation operations such as OTP or biometric scanners.

  • Gateway SCSP and Portal do not allow a bucket with object locking to be deleted, even if it is empty. It must be deleted by an S3 client e.g. using "rclone purge" to delete all objects and versions. (CLOUD-3516)

...