# Manticore Search 9.2.14: Boolean Query Optimization, Fuzzy Search Improvements and Bug Fixes

Manticore Search 9.2.14 introduces enhanced fuzzy search and numerous bugfixes

We're excited to announce the release of **Manticore Search 9.2.14**, bringing `boolean_simplify` by default, fuzzy search improvements and numerous bug fixes to improve stability and reliability.

---

### 🛠️ New Features and Improvements

This release includes several notable enhancements:

- **Fuzzy Search Enhancement** ([Issue #490](https://github.com/manticoresoftware/manticoresearch-buddy/issues/490)): Improved [fuzzy search](https://manual.manticoresearch.com/Searching/Spell_correction#Fuzzy-Search) to better find terms like "defghi" when searching for "def ghi".

- **Boolean Simplify Enabled by Default** ([Issue #3058](https://github.com/manticoresoftware/manticoresearch/pull/3058)): The [boolean_simplify](https://manual.manticoresearch.com/Searching/Options#boolean_simplify) option is now enabled by default, optimizing query execution.

---

### ⚠️ Breaking Changes

This release includes two breaking changes that require attention:

* **HTTP JSON Response Change** ([Issue #3165](https://github.com/manticoresoftware/manticoresearch/issues/3165)): Changed `_id` to `id` in some HTTP JSON responses for consistency. Make sure to update your application code accordingly.
* **Server ID Check for Cluster Joins** ([Issue #3186](https://github.com/manticoresoftware/manticoresearch/issues/3186)): Added a check for `server_id` during cluster joins to ensure each node has a unique ID. The `JOIN CLUSTER` operation can now fail with an error message indicating a duplicate [server_id](https://manual.manticoresearch.com/Server_settings/Searchd#server_id).
   To resolve this issue:
     - Ensure that each node in the replication cluster has a unique [server_id](https://manual.manticoresearch.com/Server_settings/Searchd#server_id).
     - You can change the default [server_id](https://manual.manticoresearch.com/Server_settings/Searchd#server_id) in the "searchd" section of your configuration file.
   
   If you are running a replication cluster, you need to:
     - First, cleanly stop all your nodes
     - Then, start the node that was stopped last with `--new-cluster`, using the tool `manticore_new_cluster` in Linux.
     - Read about [restarting a cluster](https://manual.manticoresearch.com/Creating_a_cluster/Setting_up_replication/Restarting_a_cluster#Restarting-a-cluster) for more details.

---

### 🔧 Critical Bug Fixes

This release addresses several important issues:

* **Stability Improvements**:
   - Fixed a crash caused by losing the scheduler after a wait; now, specific schedulers like `serializer` are properly restored ([Commit 6fda](https://github.com/manticoresoftware/manticoresearch/commit/6fdad3923dd6953f4b781943eed5ec5c28b7f808))
   - Fixed a crash when decoding invalid base64 input ([Issue #3119](https://github.com/manticoresoftware/manticoresearch/issues/3119))
   - Fixed a crash when building a secondary index on an empty JSON column ([Issue #3123](https://github.com/manticoresoftware/manticoresearch/issues/3123))
   - Fixed a crash caused by duplicate entries ([Issue #3138](https://github.com/manticoresoftware/manticoresearch/issues/3138))
* **Query and Join Improvements**:
   - Fixed a bug where weights from the right joined table couldn't be used in the `ORDER BY` clause ([Commit c333](https://github.com/manticoresoftware/manticoresearch/commit/c333b277d4a504de5fe298e9ab570a9f9ea31e0a))
   - Fixed an issue where `fuzzy=1` option couldn't be used with `ranker` or `field_weights` ([Issue #3151](https://github.com/manticoresoftware/manticoresearch/issues/3151))
   - Fixed a bug where `SET GLOBAL timezone` had no effect ([Issue #3163](https://github.com/manticoresoftware/manticoresearch/issues/3163))
   - Fixed: `UPDATE` statements now correctly respect the `query_log_min_msec` setting ([Issue #3189](https://github.com/manticoresoftware/manticoresearch/issues/3189))
* **Data Handling and Replication**:
   - Fixed an issue with handling uppercase table names during auto-schema inserts ([Issue #3018](https://github.com/manticoresoftware/manticoresearch/issues/3018))
   - Fixed an issue where text field values could be lost when using IDs larger than 2^63 ([Issue #3181](https://github.com/manticoresoftware/manticoresearch/issues/3181))
   - Fixed a race condition when saving real-time disk chunks that could cause `JOIN CLUSTER` to fail ([Issue #3247](https://github.com/manticoresoftware/manticoresearch/issues/3247))

---

## 🚀 Get Started Today

Upgrade to **Manticore Search 9.2.14** to take advantage of these powerful new features and improvements. For a full list of changes, visit the [changelog](https://manual.manticoresearch.com/Changelog).

**We'd love to hear from you!**
- Join the discussion on our [Community Forum](https://forum.manticoresearch.com)
- Report issues or suggest features on [GitHub](https://github.com/manticoresoftware/manticoresearch/issues)
- Chat with us on [Slack](https://slack.manticoresearch.com)
- Email us directly at `contact@manticoresearch.com`