Key highlights
Commerce Studio support
Managed Fusion 5.9.8 is fully compatible with Commerce Studio, Lucidworks’ solution for enhancing e-commerce experiences. Commerce Studio will be generally available at the end of January, 2025. Accompanying that release will be documentation and training materials.LucidAcademyLucidworks offers free training to help you get started.The Course for What is Commerce Studio? focuses on how to tailor your user’s search and browse experiences through powerful rule building, merchandising, audience segmentation, and more:
Expanded availability for ConfigSync
Lucidworks has long utilized ConfigSync internally for Managed Fusion environments to maintain consistent and up-to-date configuration settings across multiple environments. Now, ConfigSync is available to self-hosted clients using Fusion 5.9.8 and later.LucidAcademyLucidworks offers free training to help you get started.The Course for ConfigSync focuses on how to set up ConfigSync, choose a synchronization mode, and apply filters:
Bug fixes
- Fixed an issue with Predictive Merchandiser that prevented saving new fields in templates.
- Fixed an issue that prevented the data model field dropdown from displaying in the Data Model Mapping index pipeline stage.
Deprecations
For full details on deprecations, see Deprecations and Removals. As part of our ongoing commitment to providing a modern, efficient, and secure product, Lucidworks is officially deprecating support for the Nashorn JavaScript engine in Managed Fusion 5.9.8. Users are advised to use the OpenJDK Nashorn engine, a robust and actively maintained alternative, for all JavaScript pipeline stages. The deprecation aligns with industry trends and ensures compatibility with modern tools and frameworks. OpenJDK Nashorn provides enhanced performance, improved support, and ongoing updates, making it the ideal replacement.FAQHow long will Lucidworks continue to support Nashorn?Nashorn will remain available for at least 6 months from the release of Managed Fusion 5.9.8. All Nashorn-related features and integrations will be removed in a release after this 6-month period.
- Audit your code. Identify all areas where Nashorn is used in your applications.
- Plan your migration. Transition your JavaScript pipelines from Nashorn to OpenJDK Nashorn. Be sure to thoroughly test compatibility with your configurations to ensure a smooth transition.
- Seek support. Lucidworks is available to assist with any migration questions or challenges. Please contact your Client Excellence team if you have any questions.
You can select the OpenJDK Nashorn engine in the pipeline views or in the workbenches:
Removals
For more information, see Deprecations and Removals.Bitnami removal
By August 28, 2025, Fusion’s Helm chart will reference internally built open-source images instead of Bitnami images due to changes in how they host images.Platform Support and Component Versions
Kubernetes platform support
Lucidworks has tested and validated support for the following Kubernetes platform and versions:- Google Kubernetes Engine (GKE): 1.28, 1.29, 1.30
Component versions
The following table details the versions of key components that may be critical to deployments and upgrades.| Component | Version |
|---|---|
| Solr | fusion-solr 5.9.8 (based on Solr 9.6.1) |
| ZooKeeper | 3.9.1 |
| Spark | 3.2.2 |
| Ingress Controllers | Nginx, Ambassador (Envoy), GKE Ingress Controller Istio not supported. |