# Manticore Search 14.1.0: Force Bigrams and Bug Fixes

Manticore Search 14.1.0: force_bigrams option, replication progress tracking, and various bug fixes

We're pleased to announce [Manticore Search 14.1.0](/install/), a release that includes our work for October 2025. This update adds the `force_bigrams` option for spell correction, replication progress tracking, and various bug fixes.

❤️ **Special thanks** to [@ricardopintottrdata](https://github.com/ricardopintottrdata) for their contributions on HAVING total counts and filter error fixes, and to [@jdelStrother](https://github.com/jdelStrother) for improving CJK segmentation handling when Jieba support isn't available.

---

## ⚠️ Important Replication Update

**Version 14.0.0** updated the replication protocol. If you're running a replication cluster, you need to:

1. **Cleanly stop all your nodes**
2. **Start the node that was stopped last** with `--new-cluster`, using the `manticore_new_cluster` tool in Linux
3. **Read about [restarting a cluster](https://manual.manticoresearch.com/Creating_a_cluster/Setting_up_replication/Restarting_a_cluster#Restarting-a-cluster)** for more details

---

## New Features and Improvements

### Force Bigrams Option
Added a `force_bigrams` option for [fuzzy](https://manual.manticoresearch.com/Searching/Autocomplete#Using-force_bigrams-for-better-transposition-handling) and [autocomplete](https://manual.manticoresearch.com/Searching/Spell_correction#Using-force_bigrams-for-better-transposition-handling) functionality. This option helps with spell correction for shorter words where trigram matching may not work as well. For example, when correcting "Geroge" to "George", bigrams can provide better matching than trigrams for such transposition cases.

### Replication Progress Tracking
Added a [progress meter](https://manual.manticoresearch.com/Creating_a_cluster/Setting_up_replication/Replication_cluster_status#SST-Progress-Metrics) for donor and joiner nodes in replication SST, visible in `SHOW STATUS`. This provides visibility into replication state synchronization progress.

### Additional Improvements
- **LOCK TABLES support**: Added for mysqldump compatibility
- **Buddy updated to 3.37.0**: Various improvements and stability fixes

---

## Bug Fixes

This release includes numerous bug fixes across multiple versions leading up to 14.1.0:

### Critical Fixes
- **Fixed crash with `max(ft field)`** - Resolved a critical crash when using max functions on full-text fields
- **Fixed empty filter name error** - Resolved error when using filters with empty names
- **Fixed full-text query crashes** - Addressed crashes caused by specific full-text query patterns
- **Fixed `"(abc|def)"` query handling** - Full-text queries with this pattern now work as expected

### Query and Search Improvements
- **Fixed HAVING total counts** - Added ability to get total number of results for queries using HAVING
- **Enhanced CALL SUGGEST** - SUGGEST can now use bigrams instead of trigrams when needed, improving spell correction for shorter words
- **Fixed CJK segmentation** - Improved `ParseCJKSegmentation` when Jieba support isn't available
- **Added expansion phrase warning** - New `searchd.expansion_phrase_warning` option for better query debugging

### Replication and Clustering
- **Fixed replication transaction handling** - Improved key generation and conflict resolution

### System and Component Updates
- **Improved FreeBSD compilation** - Fixed native FreeBSD build issues
- **Enhanced Filebeat compatibility** - Added testing for Filebeat version 9.2
- **Better error handling** - Improved error handling for right-joined JSON queries
- **KNN parameter validation** - Added proper validation for KNN parameters

---

## Compatibility

Manticore Search 14.1.0 maintains **strong backward compatibility** with important considerations:

### General Compatibility
- **Fully compatible** with existing data and queries

### Replication Cluster Considerations
⚠️ **Important**: Version 14.0.0 introduced replication protocol changes. If upgrading from pre-14.0.0 versions with replication clusters:

1. **Plan downtime** for proper cluster restart procedure
2. **Follow the cluster restart guide** carefully
3. **Test the upgrade** in a staging environment first

To upgrade, follow the [installation guide](/install/).

## Need help or want to connect?

- Join our [Slack](https://slack.manticoresearch.com)  
- Visit the [Forum](https://forum.manticoresearch.com)  
- Report issues or suggest features on [GitHub](https://github.com/manticoresoftware/manticoresearch/issues)  
- Email us at `contact@manticoresearch.com`  

For full details, see the [Changelog](https://manual.manticoresearch.com/Changelog#Version-14.1.0).