Skip to main content
Release date: December 13, 2022 Component versions:
ComponentVersion
Solrfusion-solr 8.11.1 (based on Solr 8.11.1)
ZooKeeper3.7.1
Spark3.2.2
KubernetesGKE, AKS, EKS 1.24 Rancher (RKE) and OpenShift 4 compatible with Kubernetes 1.24 OpenStack and customized Kubernetes installs not supported. See Kubernetes support for end of support dates.
Ingress ControllersNginx, Ambassador (Envoy), GKE Ingress Controller Istio not supported.
More information about support dates can be found at Lucidworks Fusion Product Lifecycle.
Looking to upgrade?Check out the Fusion 5 Upgrades for details.
Looking to upgrade?See Fusion 5 Upgrades for detailed instructions.

​
Improvements

​
Fusion

  • 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.

​
Fusion Connectors

  • The recrawl 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.
Follow this configuration to use a remote connector in Fusion.
A known issue is after idling for five minutes without any new connector start requests, the remote connector stops responding to server requests and must restart. This causes connector start requests to hang. A workaround is to schedule a connector to run every three minutes. It is recommended to use a connector instance that doesn’t fetch any documents to keep the remote connector functional without frequent restarts.
  1. Execute the following command. 
    java -jar connector-plugin-client-standalone.jar [YAML_CONFIG_FILE]
  2. Check that the YAML_CONFIG_FILE has the following format. 
    kafka-bridge:
    target: mynamespace-connectors-backend.lucidworkstest.com:443 # mandatory
    plain-text: false # optional
    proxy-server: # optional - needed when a forward proxy server is used to provide outbound access to the standalone connector
    host: host
    port: 111
    user: user
    password: password
    trust: # optional - needed when the client’s system doesn’t trust the server’s certificate
    cert-collection-filepath: path1

proxy: # mandatory fusion-proxy
user: admin
password: password123
url: https://fusiontest.com/ # needed only when the connector plugin requires blob store access

plugin: # mandatory
path: ./fs.zip
type:
    suffix: remote
  3. Use this table for descriptions of the YAML properties.
KeyValue description
kafka-bridge.targetThe Kafka-gRPC bridge host:port pair.
kafka-bridge.plain-textEnable when TLS ingress is not used.
kafka-bridge.proxy-server.hostThe Forward Proxy Server Host.
kafka-bridge.proxy-server.portThe Forward Proxy Server Port.
kafka-bridge.proxy-server.userThe Forward Proxy Server User.
kafka-bridge.proxy-server.passwordThe Forward Proxy Server Password.
kafka-bridge.trust.cert-collection-filepathThe Private Key file path.
proxy.urlFusion proxy url.
proxy.userFusion proxy user.
proxy.passwordFusion proxy password.
plugin.pathThe path of the plugin zip file.
plugin.typeOptional suffix added to the plugin id. For example, if the plugin id is lucidworks.test and the suffix is remote, the plugin will be launched with lucidworks.test.remote.
Example YAML_CONFIG_FILE:
kafka-bridge:
target: mynamespace-connectors.example.com:443
plain-text: false

proxy:
user: admin
password: "password123"

plugin:
path: ./testplugin.zip

​
Predictive Merchandiser

  • Improved UI elements in the Predictive Merchandiser.

​
Bug Fixes

​
Fusion

  • 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.

​
Fusion Connectors

  • 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.

​
Predictive Merchandiser

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

​
Known issues

  • New Kerberos security realms cannot be configured successfully in this version of Fusion.
  • A bug was discovered in the Spark 3.2.x component that prevents signal aggregation for signals stored in the cloud in Parquet format. For more information about the issue, see the Spark bug report.
    This issue is fixed in Fusion 5.7.1.

​
Removals

  • Removed deprecated NLP Annotator stage from Query Workbench and OpenNLP NER stage from Index Workbench.
⌘I