manticoresoftware/manticoresearch release-15.1.0

Manticore Search 15.1.0

on GitHub

Version 15.1.0

Released: December 7th 2025

Recommended Libraries

• Recommended MCL version: 9.0.0
• Recommended Buddy version: 3.40.2

If you follow the official installation guide, you don't need to worry about this.

Breaking Changes

• ⚠️ v15.0.0 PR #4003 Updated MCL requirement to 9.0.0, bringing uncompressed float-vector storage, block-size change for KNN vectors, and non-buffered reads. This update changes the data format. Older MCL versions won’t be able to read it, but the new version can still read your existing columnar tables without any issues.

New Features and Improvements

• 🆕 v15.1.0 PR #3990 Improved disk chunk flushing log records by breaking the total time into clearer parts.
• 🆕 v14.7.0 Issue #3860 Updated Buddy requirement to 3.40.1, which includes an improvement in autocomplete: normalized bigram-separator characters to spaces and filtered out duplicate or malformed suggestion combinations to improve suggestion quality. It also includes a fix for invalid JSON errors in Kafka views and a fix for autocomplete so sorting combinations no longer throws errors when some keys are missing in the score map.
• 🆕 v14.6.0 Issue #615 Updated the Manticore Buddy requirement to version 3.39.1, which includes a fix for invalid JSON errors in the KNN plugin and allows Buddy handlers to override the HTTP Content-Type so /metrics now returns Prometheus text format (text/plain; version=0.0.4) instead of JSON, fixing scraping failures.
• 🆕 v14.4.0 PR #3942 Updated the Manticore Buddy requirement to 3.38.0, filtering out zero-doc suggestions, improving string-key handling with Ds\Map, changing memory-usage reporting format in Buddy from KB to bytes for greater precision and enhancing performance, stability, and maintainability.
• 🆕 v14.5.0 Issue #3329 Trim extra whitespace and new lines in JSON payloads when logging query requests — skip leading/trailing spaces to avoid logging malformed JSON.
• 🆕 v14.3.0 PR #3932 Improved handling of LOCK TABLES / UNLOCK TABLES: write locks now return warnings instead of errors, read locks are correctly shown in SHOW LOCKS, and the overall lock logic behaves consistently.
• 🆕 v14.2.0 Issue #3891 Added support for arbitrary filter expressions in JOIN ON clauses (not just equality comparisons), enabling queries like ... ON t1.id = t2.t1_id AND t2.value = 5.

Bug Fixes

• 🪲 v15.0.6 Issue #3601 Fixed a regression where the native Windows service failed to start when installed with a custom configuration path.
• 🪲 v15.0.5 Issue #3864 Fixed handling of "joined fields" in SQL-based sources so that an "end marker" gets set correctly when iterating joined hits.
• 🪲 v15.0.4 Issue #4004 Fixed a regression where HTTP /sql responses from the daemon incorrectly used the Content-Type: text/html header instead of application/json.
• 🪲 v15.0.3 Issue #2727 Fixed issue where grouping via GROUP BY / FACET on attributes generated with a JSON-to-attribute mapping failed to work.
• 🪲 v15.0.2 Issue #3962 Updated the Buddy requirement to 3.40.2, which adds fuzzy-search support to the /sql endpoint and includes other fuzzy-search fixes.
• 🪲 v15.0.1 PR #3922 Updated the documentation and tests related to supporting Logstash 9.2.
• 🪲 v14.7.6 PR #4002 Fixed KNN oversampling behavior: no longer compute rescored KNN distance when rescoring is not requested, and pass float-vector access hints through to the columnar storage layer.
• 🪲 v14.7.5 PR #3999 Fixed the “test_298” model to resolve a failing KNN-related test.
• 🪲 v14.7.4 Issue #3977 Tests on Windows sometimes produced .mdmp crash dumps — fixed so "ubertests" no longer leave minidumps after completion.
• 🪲 v14.7.3 Issue #3832 Fixed a bug where multi-query requests via /cli_json that include semicolons (e.g. combining SQL statements) failed — semicolons are no longer replaced with null characters before processing.
• 🪲 v14.7.2 Issue #1613 Documented the internal 32-bit mask used when counting ranking factors for Phrase/Proximity/NEAR operators and how it can undercount terms beyond the 31st keyword.
• 🪲 v14.7.1 PR #3992 Fixed missing error messages for HTTP UPDATE and DELETE requests on distributed tables handled via agents, so clients now correctly receive errors when operations fail.
• 🪲 v14.6.4 Issue #3478 Enhanced update validation to check that updated attributes do not conflict with full-text fields; updates now reject modifications if they target full-text fields.
• 🪲 v14.6.3 Issue #2352 Fixed an internal error when using distributed tables with persistent_connections_limit.
• 🪲 v14.6.2 Issue #3757 Fixed a bug where table-status counters misleadingly labeled with "_sec" (e.g. query_time_1min) actually reported milliseconds instead of seconds.
• 🪲 v14.6.1 Issue #3979 Fixed a bug where SHOW INDEX <name> STATUS search timing stats (search_stats_ms_*) did not match the values calculated from the query logs; the reported timings now reflect the real logged query times.
• 🪲 v14.5.8 Issue #3517 Updated HTTP header handling so that Buddy integrations can define or override headers instead of always forcing application/json.
• 🪲 v14.5.7 Fixed test 226 to enforce a stable result order, and corrected the GTest model for JSON mixed-array handling.
• 🪲 v14.5.6 Fixed Windows build by correcting a type mismatch in binlog.cpp, ensuring DoSaveMeta() now compiles correctly for Windows platforms.
• 🪲 v14.5.5 Issue #805 Issue #807 Issue #3924 Fixed inconsistent behavior in JSON-attribute faceting: aliasing a JSON array in a FACET clause now behaves the same as faceting on the array directly.
• 🪲 v14.5.4 Issue #3927 Fixed a crash in KNN vector search by skipping searches on empty HNSW indexes.
• 🪲 v14.5.2 Issue #3669 Fixed MATCH() parsing so empty groups like () no longer trigger an error (e.g. queries such as camera() now work correctly).
• 🪲 v14.5.1 PR #3961 Updated backup documentation for mysqldump replication mode: explained using --skip-lock-tables when dumping replicated tables, and fixed several broken manual links.
• 🪲 v14.3.2 Issue #2772 Fixed a bug where some commands executed via MySQL client 9 caused a "unexpected $undefined near '$$'" error in the query log.
• 🪲 v14.3.1 PR #3934 Updated the Manticore Buddy requirement from 3.37.0 to 3.37.2, removing redundant LOCK/UNLOCK TABLES checks (now handled by the daemon) and fixing autocomplete parsing so queries with escaped quotes (e.g. \" or \') are handled correctly instead of failing.
• 🪲 v14.2.1 Issue #3602 Fixed a crash when using knn_dist() in a custom ranker expression with KNN+MATCH queries; such queries now return a clear error instead of crashing.
• 🪲 v14.1.1 docs: fixed minor translation issues.