Fusion 5.7.0Release Notes

Fusion now supports Kubernetes 1.24. This applies to GKE, AKS, and EKS. It also applies to Rancher (RKE) and OpenShift 4 versions that are compatible with Kubernetes 1.24.

Fusion now uses a custom Solr image called fusion-solr. This version of Solr is based on Solr 8.11.1 and adds functionality to support Fusion features.

Upgraded Fusion to use Tika 2.4.1.

Disabled browser autofill in Fusion data source configuration forms to prevent accidentally filling fields incorrectly.

The incremental crawl process is updated for the LDAP ACLs V2 connector. For more information, see LDAP ACLs V2 connector incremental crawls.

As part of the transition from Pulsar to Kafka, the ability to Remotely Launch a Plugin is returned.

A new connector, the Web V2 Connector, is added. This brings our Web connector from the classic framework to our V2 framework.

The Kaltura V2 Connector is now available.

Improved UI elements in the Predictive Merchandiser.

Fixed an issue where pointing a Fusion collection at a Solr collection with a different name breaks queries to solrServer in Javascript stages.

Fixed an issue when adding a new Graph security trimming stage; now you can enter a comma-separated list of datasources in Exclude Data Source ID(s) and Inclusive Data Source ID(s) fields with spaces. For example, ds1, ds2, ds3.

Fixed an issue where documentation links pointed to Fusion 5.4 version, instead of the currently used version of Fusion.

The LDAP ACLs V2 connector is updated to reduce crawl bugs, prevent a false error from reporting when the crawl is stopped, and ensure permissions settings are kept in sync.

Fixed an issue with network policies that prevented the Sharepoint Optimized V2 connector plugin from indexing some data.

Fixed an issue with the ServiceNow connector where empty fields would cause an error and break the crawl.

Made the text box size larger to make it easier to enter multiple Boost Queries in the Rules Manager.