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

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): Improved fuzzy search to better find terms like "defghi" when searching for "def ghi".
Boolean Simplify Enabled by Default (Issue #3058): The 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): 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): 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. To resolve this issue:
- Ensure that each node in the replication cluster has a unique server_id.
- You can change the default 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 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)
- Fixed a crash when decoding invalid base64 input (Issue #3119)
- Fixed a crash when building a secondary index on an empty JSON column (Issue #3123)
- Fixed a crash caused by duplicate entries (Issue #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)
- Fixed an issue where fuzzy=1 option couldn't be used with ranker or field_weights (Issue #3151)
- Fixed a bug where SET GLOBAL timezone had no effect (Issue #3163)
- Fixed: UPDATE statements now correctly respect the query_log_min_msec setting (Issue #3189)
Data Handling and Replication:
- Fixed an issue with handling uppercase table names during auto-schema inserts (Issue #3018)
- Fixed an issue where text field values could be lost when using IDs larger than 2^63 (Issue #3181)
- Fixed a race condition when saving real-time disk chunks that could cause JOIN CLUSTER to fail (Issue #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.

We'd love to hear from you!