Cloud CMS Release 3.2.74

The following are the new features, enhancements and fixed issues for the Cloud CMS 3.2.74 release.

CVE-2021-44228

This release is hardened against CVE-2021-44228. For more information on CVE-2021-44228, please visit:
https://gitana.io/documentation/docker/notices/cve-2021-44228.html

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-74.html

New Features

General Support for AWS OpenSearch 7.x

General Support for ElasticSearch 7.x

General Support for MongoDB 4.x

For supported stack information, see:
https://gitana.io/documentation/supported-stacks/32.html

Enhancements

Job Queue

  • The Job Reaper thread is now enabled by default with a configuration that enables it to clean up older job records more promptly.

Logging

  • Request logging context now includes body (for JSON payloads). This information is automatically logged to the default rolling file appender and is also applied to Kinesis, Cloud Watch and other configured appenders.

Performance

  • Reduced the number of cache writes that occur when retrieving nodes or roles so as to improve overall API throughput.
  • Improved cache speed by streamlining some unneeded initializers and event listening subsystems.
  • Faster localization of nodes via the API.

Bug Fixes

Binary Storage

  • Fix so that cleanup logic on Caching Binary storage system runs within a try/catch to handle cases where files may fail to write to back end provider.

Branch

  • Fix so that cluster branch initialization works more efficiently for cases where containers come online and multiple threads may contend for first access to a branch.

Indexing

  • Fix so that adhoc creation of MongoDB indexes strictly uses background mode for legacy, older databases.
  • Fix so that includes and excludes arrays properly parse when making a repair indexes call.

  • Fix so that pagination defaults and maximums are always applied and enforced for cases where branch-level node queries pull back a constrained subset of fields.

Transfer

  • Fix so that exported nodes that have an incorrectly identified changeset will auto-correct and export for the correct changeset.









Ready to Get Started?

Unlock your data with smart content services and real-time deployment


Try Gitana for free Ask for a demo