> ## Documentation Index
> Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Fusion 5.7.0
[localhost link]: http://localhost:3000/docs/5/fusion/release-notes/5.7.0-release-notes
[mintlify link]: https://doc.lucidworks.com/docs/5/fusion/release-notes/5.7.0-release-notes
[old doc.lw link]: https://doc.lucidworks.com/fusion/5.9/3c6x8l
**Release date:** December 13, 2022
**Component versions:**
| Component | Version |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Solr** | fusion-solr 8.11.1 *(based on Solr 8.11.1)* |
| **ZooKeeper** | 3.7.1 |
| **Spark** | 3.2.2 |
| **Kubernetes** | GKE, AKS, EKS 1.24 Rancher (RKE) and OpenShift 4 compatible with Kubernetes 1.24 OpenStack and customized Kubernetes installs not supported. See [Kubernetes support](/docs/policies/lifecycle-policies/lw-version-support-lifecycle#kubernetes-support) for end of support dates. |
| **Ingress Controllers** | Nginx, Ambassador (Envoy), GKE Ingress Controller Istio not supported. |
**More information about support dates can be found at [Lucidworks Fusion Product Lifecycle](/docs/policies/lifecycle-policies/lw-version-support-lifecycle).**
**Looking to upgrade?**
See [Fusion 5 Upgrades](/docs/5/fusion/operations/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](/docs/fusion-connectors/connectors/ad-acl-ldap).
* 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.
```yaml theme={"dark"}
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.
| Key | Value description |
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `kafka-bridge.target` | The Kafka-gRPC bridge host:port pair. |
| `kafka-bridge.plain-text` | Enable when TLS ingress is not used. |
| `kafka-bridge.proxy-server.host` | The Forward Proxy Server Host. |
| `kafka-bridge.proxy-server.port` | The Forward Proxy Server Port. |
| `kafka-bridge.proxy-server.user` | The Forward Proxy Server User. |
| `kafka-bridge.proxy-server.password` | The Forward Proxy Server Password. |
| `kafka-bridge.trust.cert-collection-filepath` | The Private Key file path. |
| `proxy.url` | Fusion proxy url. |
| `proxy.user` | Fusion proxy user. |
| `proxy.password` | Fusion proxy password. |
| `plugin.path` | The path of the plugin zip file. |
| `plugin.type` | Optional 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`:
```yaml theme={"dark"}
kafka-bridge:
target: mynamespace-connectors.example.com:443
plain-text: false
proxy:
user: admin
password: "password123"
plugin:
path: ./testplugin.zip
```
* A new connector, the [Web V2 Connector](/docs/fusion-connectors/connectors/web-v2), is added. This brings our Web connector from the classic framework to our V2 framework.
* The [Kaltura V2 Connector](/docs/fusion-connectors/connectors/kaltura) is now available.
### 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](/docs/fusion-connectors/connectors/ad-acl-ldap) 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](https://issues.apache.org/jira/browse/SPARK-38318).
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.