> ## 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.
# Lucidworks Search 5.9.15
[localhost link]: http://localhost:3000/docs/lucidworks-search/13-release-notes/5.9.15-release-notes
[mintlify link]: https://doc.lucidworks.com/docs/lucidworks-search/13-release-notes/5.9.15-release-notes
Released on October 16, 2025, Lucidworks Search 5.9.15 is a [maintenance release](/docs/policies/lifecycle-policies/lw-version-support-lifecycle#maintenance-release-support-policy) that includes scalability enhancements to LWAI stages, accuracy improvements in the Consumption Dashboard entitlement reporting, security fixes, and updated UI behavior.
**Security patch for api-gateway**
Lucidworks will apply a security patch to your Lucidworks Search instance to address critical Netty request smuggling vulnerabilities (CVE-2026-42581, CVE-2026-42585, CVE-2026-42587) in the `api-gateway` service.
No action is required on your part.
For supported Kubernetes versions and key component versions, see [Platform support and component versions](#platform-support-and-component-versions).
## Key highlights
### Consumption and entitlement updates
The Consumption Dashboard is enhanced to make consumption tracking more accurate for entitlement monitoring.
{/* * Temporary pipelines are now excluded from reports. Previously these pipelines were listed in reports and had to be manually unchecked to exclude them. Excluding temporary pipelines decreases report noise and ensures that results only reflect production workloads. */}
{/* * Record totals are adjusted to exclude signals and aggregations. Excluding these counts improves entitlement tracking accuracy by removing non-content collections. */}
{/* * The hover interaction for **requests per pipeline** graphs now displays a sortable list of pipelines to make it easier to analyze pipeline-level consumption. */}
The [Consumption dashboard](/docs/lucidworks-search/08-administration/monitoring/consumption) uses graphs to visually track request and document usage against the allotted consumption for your Lucidworks Search license. The hover interaction for **requests per pipeline** graphs now displays a sortable list of pipelines to make it easier to analyze pipeline-level consumption.
Pipelines in a **requests per pipeline** graph can be sorted in the following ways:
* **Value descending**: sort pipelines according to number of requests from most to least.
* **Value ascending**: sort pipelines according to number of requests from least to most.
* **Alphabetically ascending**: sort by pipeline name from A to Z.
* **Alphabetically descending**: sort by pipeline name from Z to A.
### New Retrieval-Augmented Generation (RAG) query stage
Lucidworks continues expanding RAG capabilities that improve the quality and accuracy of LLM-powered retrieval workflows.
Documents that require chunking tend to be large and cover multiple topics.
Queries return an answer that links to the document, but the answer does not show exactly *where* to find that information in the document.
A [Chunking RAG Bridge Query Stage](/docs/lucidworks-search/09-developer-documentation/config-specs/query-pipeline-stages/chunking-rag-bridge) is introduced to evolve RAG from document-level retrieval to chunk-level precision.
With this new stage, each cited source that accompanies a RAG answer also provides a link to the relevant document along with a snippet containing information about where to find the content in the document.
### New Batch Vectorize index stage
Fusion 5.9.15 introduces an [LWAI Batch Vectorize Index Stage](/docs/lucidworks-search/09-developer-documentation/config-specs/index-pipeline-stages/lwai-batch-vectorize) for AI pipelines.
This works the same as the [LWAI Vectorize Field stage](/docs/lucidworks-search/09-developer-documentation/config-specs/index-pipeline-stages/vectorize-field-via-lucidworks-ai-index-stage) but delivers faster indexing throughput because it processes your documents in batches before sending those documents to the next stage in your index pipeline. The LWAI Batch Vectorize stage can improve document indexing performance up to ten times the rate of the LWAI Vectorize Field stage.
The LWAI Vectorize stage processes documents one at a time.
With the LWAI Batch Vectorization Index stage, Lucidworks Search can send multiple documents per API call, reducing API overhead and improving scalability.
This stage includes new properties.
A batch is forwarded to the API as soon as it is full or when the wait time elapses, whichever comes first.
Maximum number of documents per batch (up to 32).
Maximum time to wait in milliseconds since the first document is buffered before proceeding.
### Restrictive mode for query pipelines
Lucidworks Search 5.9.15 introduces restrictive mode, giving you more control and security over query pipelines.
When you enable restrictive mode, Fusion enforces stricter query parameter validation and sanitization, blocking unsafe inputs and limiting potentially expensive operations.
This update makes your search environment more secure and reliable.
See [Restrictive Mode](/docs/lucidworks-search/05-move-data-out/query-pipeline/restrictive-mode) for complete details about how restrictive mode works and how to enable it.
### Lucidworks Search Admin UI updates
Several updates to the Lucidworks Search Admin UI improve safety and usability:
* A description is added to the JSON Facets stage, clarifying its purpose.
* UI labels are added for Ray model deployment jobs, grouping them under “Model Deployment Jobs” for clarity and discoverability.
* The **Asynchronous Execution Config** checkbox for the AI pipeline stages is now properly aligned with its label for better visual consistency and user experience.
### Naming conventions for AI-generated fields
Fields generated by Lucidworks AI now include a prefix of `lwai_` when indexed to Solr, making it easier to identify those fields when excluding them or using them for other tasks, such as rules, queries, or reports. Any field names previously generated are still supported and no changes are needed to continue using them.
### Additional Selenium support for the Web V2 connector
For users of the [Web V2 connector](/docs/fusion-connectors/connectors/web-v2) v2.2.1 and later, Fusion 5.9.15 improves support for Selenium Grid. The Selenium service is now installed automatically with the Web V2 connector and removed automatically when the connector is removed, resulting in faster setup and ease of use.
### Smarter hybrid search
Resiliency is improved for searches using the [Neural Hybrid Query stage](/docs/lucidworks-search/09-developer-documentation/config-specs/query-pipeline-stages/neural-hybrid-query-stage).
When a hybrid query depends on vectorization, failures in the upstream vectorization stage previously resulted in incomplete or unstable search behavior.
Now Lucidworks Search automatically switches to lexical-only search if vectorization is unavailable to ensure uninterrupted results.
Clear indicators and improved logging make it easier to understand when the fallback occurs:
* If no vector is produced, you will see the message: `Input vector value is blank, skipping vector processing`.
* If a vector exists but is empty, you will see the message: `Input vector value is empty, {}, skipping vector processing`.
### Ability added for Prediction API
The Prediction API now supports [image metadata enrichment](/docs/lw-platform/lw-ai/lw-ai-apis/lw-ai-prediction-api/image-metadata-enrichment). This API use case generates keywords and categories for images. This information can then be used as metadata for SEO, image-based product discovery, and more.
### Enhanced previews for integrated Lucidworks Platform products
{/* FUS-7813 - Preview pipeline overrides refactoring */}
A new, system-level API was added to Fusion 5.9.15 that allows Commerce Studio and other Lucidworks Platform products to simulate configuration changes before they are published. This change supports the following improvements:
* **Improved safety:** Test and validate changes without affecting live search traffic, reducing the risk of errors or downtime.
* **Faster iteration:** Experiment and refine configurations in real time, improving development speed and decision-making.
* **Higher confidence in publishing:** Preview query behavior before deployment to increase trust in changes and reduce rollback events.
Beginning with Fusion 5.9.15, all Commerce Studio integrations must have the `POST:/query/*/preview` and `GET,POST,PUT:/query-pipelines/**` permissions assigned to both the `lwp_user` and `lwp_service_account` roles in Fusion. Verify that your roles meet the following requirements:
```bash lines highlight={3-4} lwp_user theme={"dark"}
GET,PUT,DELETE,POST,HEAD:/query/experience-manager/**
GET,POST:/query/*
POST:/query/*/preview
GET,POST,PUT:/query-pipelines/**
GET:/suggestions/**
GET:/solr/*/terms
PUT,POST,GET:/apps/*/query-pipelines/**
GET:/apps/*/query-profiles/**
GET,PUT:/apps/*
GET:/solr/*/admin/luke
GET:/solr/**
```
```bash lines highlight={3-4} lwp_service_account theme={"dark"}
GET,PUT,DELETE,POST,HEAD:/query/experience-manager/**
GET,POST:/query/*
POST:/query/*/preview
GET,POST,PUT:/query-pipelines/**
GET:/suggestions/**
GET:/solr/*/terms
PUT,POST,GET:/apps/*/query-pipelines/**
GET:/apps/*/query-profiles/**
GET,PUT:/apps/*
GET,DELETE,PATCH,PUT,POST,HEAD:/apps/*/query-rewrite/**
GET,HEAD:/templating/**
GET:/solr/*/admin/luke
GET:/solr/**
```
## Bug fixes
* Added a custom module that serializes Nashorn `undefined` values as JSON `null`, preventing serialization errors when such values appear in Java objects. When using the OpenJDK version of Nashorn, an exception was thrown when the context contained keys with undefined JavaScript values. This exception occurred because the class for the undefined values was not visible outside of the OpenJDK Nashorn package. A custom object mapper is added for the class so serialization issues are now resolved when handling `undefined` in JavaScript pipeline to run reliably under Java 17.
* Time zone conversion issues are fixed in the Consumption Dashboard that caused counts to span extra days. Local times were being converted to UTC, creating an overlap that included counts for both the selected day and the following day. Removing this conversion and using only the local time ensures accurate daily totals for entitlement reporting.
* Addressed an issue where jobs are stuck in a running state during an upgrade. Allowing all crawl jobs to complete before performing Lucidworks Search upgrades is necessary to maintain data integrity and prevent invalid job states. Now requests to stop jobs during an upgrade process are enhanced to check for invalid states, attempt automatic fixes, and provide detailed status messages.
* Adjusted license checks when apps-manager is unavailable for consistent and predictable license validation behavior. In previous releases, if apps-manager was unavailable or license capabilities could not be verified, the license check could not complete. The addition of broader exception catching when retrieving license capabilities and improved error logging for service unavailability ensures predictable capability behavior while connectivity is restored.
* Fixed a permissions flow in the Fusion indexing path used by V2 connectors. REST calls made from index pipelines using V2 connectors were running without the required permissions. This returned insufficient permissions errors and skipped mapped fields. REST calls in index pipelines now execute as expected when using the required privileges.
* Fixed an error where the Tika asynchronous parser in Fusion 5.9.12 did not index the body field for SharePoint connector documents, such as DOCS, PPTX, and XLSX files. Documents were split into multiple parts, so the body content only ended up in child documents, while the parent document lacked the body field. Now the first parsed part of the document is sent to Fusion using the parent document ID so the body field merges into the expected parent document. This restores expected content extraction and preserves child parts for images and other embeds.
## Deprecations
For full details on deprecations, see [Deprecations and Removals](/docs/lucidworks-search/deprecations-and-removals).
### Deprecated jobs
The following jobs are deprecated in this release and will be removed in a future release:
* [Head/Tail Analysis](/docs/lucidworks-search/09-developer-documentation/config-specs/jobs/head-tail-analysis)
* [Phrase Extraction](/docs/lucidworks-search/09-developer-documentation/config-specs/jobs/phrase-extraction)
* [Synonym Detection](/docs/lucidworks-search/09-developer-documentation/config-specs/jobs/synonym-detection)
* [Token and Phrase Spell Correction](/docs/lucidworks-search/09-developer-documentation/config-specs/jobs/token-phrase-spell-correction)
Lucidworks recommends migrating to [Neural Hybrid Search](/docs/lucidworks-search/11-vector-search/overview), which achieves superior relevance compared to these legacy machine learning methods.
Rules previously generated by these jobs and promoted to the `_query_rewrite` collection will remain until you delete them.
## 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.29, 1.30, 1.31, 1.32, 1.33
For more information on Kubernetes version support, see the [Kubernetes support policy](/docs/policies/lifecycle-policies/lw-version-support-lifecycle#kubernetes-support).
### 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.15 *(based on Solr 9.6.1)* |
| ZooKeeper | 3.9.1 |
| Spark | 3.4.1 |
| Ingress Controllers | Nginx, Ambassador (Envoy), GKE Ingress Controller |
| Ray | ray\[serve] 2.46.0 |
More information about support dates can be found at [Lucidworks Search Product Lifecycle](/docs/policies/lifecycle-policies/lw-version-support-lifecycle).