Content Gateway 8.0.3 Release

Changes

  • Several Elasticsearch search improvements for bucket listing performance improvement. (CLOUD-3959, CLOUD-3965, CLOUD-3969, CLOUD-3950, CLOUD-3973, CLOUD-3953)

  • An empty <ListVersionsResult> XML element is now returned with every versioned listing response, even when the bucket does not have versioning enabled. (CLOUD-3965)

  • Fixed an error where an S3 listing uses a "prefix" longer than 1000 characters. The fix requires:

    • The prefix ends with the delimiter character "/".

    • The search feed is created with search.enableDelimiterPaths=true. It is the default value since Swarm 15.0. (CLOUD-3684)

  • The misleading ERROR log messages are similar to: “

    • XmlUtil: Document root element ‘ObjectLockConfiguration’, must match DOCTYPE root ‘null’.

    • XmlUtil: Document is invalid: no grammar found.” will no longer appear.
      The previous workaround of restricting the “com.caringo.gateway.util.XmlUtil" logger to FATAL is no longer required and may be removed. (CLOUD-3765)

Upgrade Impacts

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

Starting with Gateway 7.8, Elasticsearch 6.8.6 is no longer supported. Remain on Gateway 7.7 until the rolling upgrade from Elasticsearch 6.8.6 to 7.5.2 is completed.

Address the upgrade impacts for this and each prior version since the currently running version:

Impacts for 8.0.3

  • Version Requirements

    • Swarm Storage 14.1.0 or higher

    • Elasticsearch 7.5.2 or 7.17.9 (required with Swarm Storage 15.3 or higher)

    • Content UI 7.9.1

    • Storage UI 3.5.0

 

 

 

See Content Gateway 7 Release Notes and Content Gateway 6 Release Notes 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 on interactive validation operations such as OTP or biometric scanners.

  • Gateway v8.0 and later versions fail to generate video clips. (CLOUD-4082)

See Content Gateway 7 Release Notes and Content Gateway 6 Release Notes for known issues from prior releases that are still applicable, apart from those appearing above as fixed.

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.