Content Gateway 7.10 Release
Changes
Added support for https://perifery.atlassian.net/wiki/spaces/public/pages/2906030180 to repatriation (pull) data from the cloud to the local Swarm cluster. Object copying is now compatible with Azure in addition to S3. Richer namespaces are now allowed with an option for folder paths. Object names containing Unicode are now supported. (CLOUD-3580)
Added ‘folder_listings usePaths’ option to improve S3 delimiter listing performance of large buckets. See https://perifery.atlassian.net/wiki/spaces/public/pages/2443810201 for new config. (CLOUD-3328)
Upgrade Impacts
See https://perifery.atlassian.net/wiki/spaces/public/pages/2443817319, to upgrade from a version of Gateway 6. See , if migrating from Elasticsearch 2.3.3 and Gateway 5.
Starting from Gateway 7.8, Elasticsearch 6.8.6 is no longer supported. Remain on Gateway 7.7 until the rolling upgrade is completed from Elasticsearch 6.8.6 to 7.5.2.
Address the upgrade impacts for this and each prior version since the currently running version:
Impacts for 7.10
Version Requirements
Swarm Storage 14.1.0 or higher
Elasticsearch 7.5.2
Content UI 7.7.0
See 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.
See 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.