> ## 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.17.1

Released on May 28, 2026, Lucidworks Search 5.17.1 is a [patch release](/docs/policies/lifecycle-policies/lw-semantic-version-support-lifecycle#patch-release-support-policy) that delivers a security update and bug fixes for Commerce rules and pipeline compatibility.

Upgrading to the latest version of Lucidworks Search offers several key benefits:

* **Access to latest features:** Stay current with the latest features and capabilities to ensure compatibility and optimal performance.
* **Simplified process:** Lucidworks Search 5.9.5 and later use an in-place upgrade strategy, making upgrades easier than ever.
* **Extended support:** Upgrading keeps you up-to-date with the latest supported Kubernetes versions, as outlined in the [Lucidworks Semantic Version Support Lifecycle](/docs/policies/lifecycle-policies/lw-semantic-version-support-lifecycle) policy.

For supported Kubernetes versions and key component versions, see [Platform support and component versions](#platform-support-and-component-versions).

## Bug fixes

### Lucidworks Search now supports numeric operators for attribute-based rules

In previous versions of Lucidworks Search, configuring numeric field conditions for Boost by Attribute, Bury by Attribute, and Block by Attribute rules required writing Solr queries directly.

Lucidworks Search now supports numeric comparison operators for attribute-based rules, eliminating the need for manual query construction.
This update also includes fixes to the underlying JSON structure to support multiple block groups separated by OR logic.

### MCP Server now starts correctly when TLS is enabled

In previous versions of Lucidworks Search, the MCP Server failed to start when TLS was enabled due to missing SSL keystore password configuration, resulting in `BadPaddingException` errors at startup.

The MCP Server configuration now includes the required SSL properties (`server.ssl.key-store-password` and `server.ssl.trust-store-password`) when TLS is enabled, allowing the server to properly decrypt the keystore and start successfully.

### Apply Rules stage now correctly combines pipeline tags and URL tags

In previous versions of Lucidworks Search, the Apply Rules stage overwrote pipeline-configured tags with user-provided URL tags when both were present, causing rules scoped to pipeline tags to stop firing.

For example, if a pipeline had `tags=pipelineTag1` and a request also included `tags=urlTag`, only rules for `urlTag` would fire.
Rules for `pipelineTag1` were silently ignored, even though the response headers correctly showed both tags.

The Apply Rules stage now combines pipeline-configured tags and URL tags so that rules for all active tags fire as expected.

{/*
### Machine Learning stage now works correctly with Neural Hybrid Query and Apply Rules

In previous versions of Lucidworks Search, using the Machine Learning stage together with the Neural Hybrid Query stage and the Apply Rules stage caused query pipeline failures. Lucidworks fixed this compatibility issue, and all three stages now work together correctly.

REMOVED FROM SCOPE: LWAI-1225 moved to Lucidworks Search 5.18 fix version
*/}

### `kubectl cp` restored after Java upgrade

A regression introduced by a previous Java base image upgrade caused `kubectl cp` commands to fail when copying files from Lucidworks Search service pods. The failure occurred because the updated base image was missing the `libpcre2-8.so.0` shared library required by the `tar` utility used internally by `kubectl cp`:

```text theme={"dark"}
tar: error while loading shared libraries: libpcre2-8.so.0: cannot open shared object file: No such file or directory
command terminated with exit code 127
```

The base image now includes the missing library, and `kubectl cp` works correctly across all Lucidworks Search service pods.

### RAG Bridge Stage no longer returns incorrect vector format error for byte vector fields after upgrade

After upgrading to Lucidworks Search 5.17.0, the RAG Bridge Stage returned an "incorrect vector format" error when processing byte vector fields, preventing RAG-based pipelines from functioning correctly.

Lucidworks Search 5.17.1 resolves this regression, and the RAG Bridge Stage now correctly processes byte vector fields.

### Security update: CVE-2026-33870 patched

Lucidworks Search 5.17.1 includes security patches for CVE-2026-33870 in the following services:

* apps-manager
* job-config
* lwai-gateway

### Prometheus metrics restored for low time scale resolution

In previous versions of Lucidworks Search, Prometheus metrics lacked resolution when viewed at low time scales because smaller time bucket intervals were missing from the metrics configuration.

Lucidworks Search 5.17.1 restores the smaller bucket intervals, and Prometheus metrics now display with correct granularity at low time scales.

## Known issues

### Streaming mode indexing fails with unquoted character errors

When indexing content in streaming mode, the Jackson library upgrade (2.13.5 → 2.19.1) introduced stricter validation. The current implementation might fail with the long requests which use a `Transfer-Encoding: chunked` header. Below is an example of a failure message, though other messages are also possible:

```
Illegal unquoted character ((CTRL-CHAR, code 13)): has to be escaped using backslash to be included in name
```

As a workaround, divide your requests into batches and send each batch as a single request with a `Content-Length` header.

## Platform support and component versions

### Kubernetes platform support

Lucidworks has tested and validated support for the following Kubernetes platforms and versions:

* **Google Kubernetes Engine (GKE):** 1.30, 1.31, 1.32, 1.33, 1.34, 1.35
* **Microsoft Azure Kubernetes Service (AKS):** 1.30, 1.31, 1.32, 1.33, 1.34, 1.35
* **Amazon Elastic Kubernetes Service (EKS):** 1.30, 1.31, 1.32, 1.33, 1.34, 1.35

Support is also offered for Rancher Kubernetes Engine (RKE and RKE2) and OpenShift 4 versions based on Kubernetes 1.30, 1.31, 1.32, 1.33, 1.34, 1.35.
Note that RKE2 may require some Helm chart modification.
OpenStack and customized Kubernetes installations *aren't* supported.

For more information on Kubernetes version support, see the [Kubernetes support policy](/docs/policies/lifecycle-policies/lw-semantic-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.17.1 *(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                                |
| Helm                | 4.1.1                                             |

For more information about support dates, see [Lucidworks Semantic Version Support Lifecycle](/docs/policies/lifecycle-policies/lw-semantic-version-support-lifecycle).