Skip to content

Releases: manticoresoftware/docker

Manticore Search 13.13.0

07 Oct 16:05
@sanikolaev sanikolaev
13.13.0
3b68644

Choose a tag to compare

View all tags
Manticore Search 13.13.0 Latest
Latest

Version 13.13.0

Released: October 7th 2025

New Features and Improvements

Bug Fixes

  • 🪲 v13.11.8 Issue #3791 Fixed a race condition between checking and invoking a fired timer.
  • 🪲 v13.11.7 Issue #1045 Fixed a systemctl warning on RHEL 8 during systemd updates by replacing the outdated path /var/run/manticore with the correct /run/manticore in the configuration. Since the configuration file was updated, you may see a warning during upgrade asking whether to keep your version or use the new one from the package. If you have a custom (non-default) configuration, it's recommended to keep your version and update the pid_file path to /run/manticore/searchd.pid.
  • 🪲 v13.11.6 PR #3766 Added support for MCL version 8.0.6.
  • 🪲 v13.11.5 PR #3767 Improved Chinese documentation translations and updated submodules.
  • 🪲 v13.11.4 PR #3765 Fixed handling of aliased joined attributes.
  • 🪲 v13.11.3 PR #3763 Fixed a crash that could occur during batched joins on string attributes and resolved an issue where filters sometimes didn't work with LEFT JOIN.
  • 🪲 v13.11.2 Issue #3065 Fixed a crash when inserting data into a columnar table with index_field_lengths enabled.
  • 🪲 v13.11.1 Issue #3751 Fixed a crash that occurred when deleting a document with embeddings enabled.
Assets 2
Loading

Manticore Search 13.11.1

13 Sep 19:22
@sanikolaev sanikolaev
13.11.1
68a8a3f

Choose a tag to compare

View all tags
Manticore Search 13.11.1

Version 13.11.1

Released: September 13th 2025

Bug Fixes

Loading

Manticore Search 13.11.0

13 Sep 15:12
@sanikolaev sanikolaev
13.11.0
06c4bc5

Choose a tag to compare

View all tags
Manticore Search 13.11.0

Version 13.11.0

Released: September 13th 2025

The main highlight of this release is Auto Embeddings — a new feature that makes semantic search as easy as SQL.
No need for external services or complex pipelines: just insert text and search with natural language.

What Auto Embeddings Offer

  • Automatic embedding generation directly from your text
  • Natural language queries that understand meaning, not just keywords
  • Support for multiple models (OpenAI, Hugging Face, Voyage, Jina)
  • Seamless integration with SQL and JSON APIs

Recommended libraries

  • Recommended MCL version: 8.0.3
  • Recommended Buddy version: 3.35.1

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

New Features and Improvements

  • 🆕 v13.11.0 PR #3746 Added "query" support in JSON queries for embeddings generation.
  • 🆕 v13.10.0 Issue #3709 The manticore-server RPM package no longer owns /run.
  • 🆕 v13.9.0 PR #3716 Added support for boolean_simplify in the configuration.
  • 🆕 v13.8.0 Issue #3253 Installed sysctl config to increase vm.max_map_count for large datasets.
  • 🆕 v13.7.0 PR #3681 Added support for alter table <table> modify column <column> api_key=<key>.

Bug Fixes

  • 🪲 v13.10.5 PR #3737 The scroll option now correctly returns all documents with large 64-bit IDs.
  • 🪲 v13.10.4 PR #3736 Fixed a crash when using KNN with a filter tree.
  • 🪲 v13.10.3 Issue #3520 The /sql endpoint no longer allows the SHOW VERSION command.
  • 🪲 v13.10.2 PR #3637 Updated the Windows installer script.
  • 🪲 v13.10.1 Fixed local time zone detection on Linux.
  • 🪲 v13.9.2 PR #3726 Duplicate IDs in columnar mode now correctly return an error.
  • 🪲 v13.9.1 PR #3333 The manual is now auto-translated.
  • 🪲 v13.8.6 PR #3715 Fixed an embeddings generation issue when all docs in a batch were skipped.
  • 🪲 v13.8.5 PR #3711 Added Jina and Voyage embedding models, along with other automatic embeddings-related changes.
  • 🪲 v13.8.4 PR #3710 Fixed a crash on joined queries with multiple facets.
  • 🪲 v13.8.3 Fixed an issue where delete/update commits in a transaction with multiple statements at the _bulk endpoint were not counted as errors.
  • 🪲 v13.8.2 PR #3705 Fixed a crash when joining by non-columnar string attributes and improved error reporting.
  • 🪲 v13.8.1 PR #3704 Fixed a crash in query embeddings when no model was specified; added embeddings string to master-agent communication; added tests.
  • 🪲 v13.7.2 PR #Buddy#589 Removed the default IDF hack for fuzzy search.
  • 🪲 v13.7.1 Issue #3454 Fixed incorrect scroll decoding with large 64-bit IDs.
  • 🪲 v13.6.9 Issue #3674 Fixed JDBC+MySQL driver/connection pool issue with the transaction_read_only setting.
  • 🪲 v13.6.8 PR #3676 Fixed a crash on an empty result set returned by the embeddings model.
Loading

Manticore Search 13.6.7

08 Aug 10:48
@sanikolaev sanikolaev
13.6.7
f9dd1c5

Choose a tag to compare

View all tags
Manticore Search 13.6.7

Version 13.6.7

Released: August 8th 2025

New Features and Improvements

  • 🆕 v13.6.0 Issue #2226 Support for explicit '|' (OR) in PHRASE, PROXIMITY, and QUORUM operators.
  • 🆕 v13.5.0 PR #3591 Automatic embedding generation in queries (Work in Progress, not production-ready yet).
  • 🆕 v13.4.0 PR #3585 Fixed logic to prefer buddy thread count from buddy_path config if set, instead of using the daemon value.
  • 🆕 v13.3.0 PR #3577 Support for joins with local distributed tables.
  • 🆕 #3647 Added support for Debian 13 "Trixie"

Bug Fixes

  • 🪲 v13.6.7 Issue #3524 Fixed an issue with saving generated embeddings in row-wise storage.
  • 🪲 v13.6.6 Issue #3563 Fixed issues with Sequel Ace and other integrations failing due to "unknown sysvar" errors.
  • 🪲 v13.6.5 Issue #3467 Fixed issues with DBeaver and other integrations failing due to "unknown sysvar" errors.
  • 🪲 v13.6.4 Issue #3524 Fixed an issue with concatenating multi-field embeddings; also fixed embedding generation from queries.
  • 🪲 v13.6.3 Issue #3641 Fixed a bug in 13.6.0 where a phrase lost all bracketed keywords except the first one.
  • 🪲 v13.6.2 Fixed a memleak in transform_phrase.
  • 🪲 v13.6.1 Fixed a memory leak in version 13.6.0.
  • 🪲 v13.5.2 Issue #3651 Fixed more issues related to full-text search fuzz testing.
  • 🪲 v13.5.1 Issue #3560 Fixed a case where OPTIMIZE TABLE could hang indefinitely with KNN data.
  • 🪲 v13.4.2 Issue #2544 Fixed an issue where adding a float_vector column could corrupt indexes.
  • 🪲 v13.4.1 Issue #3651 Added fuzz testing for full-text parsing and fixed several issues found during testing.
  • 🪲 v13.3.1 Issue #3583 Fixed a crash when using complex boolean filters with highlighting.
  • 🪲 v13.2.7 Issue #3481 Fixed a crash when HTTP update, distributed table, and wrong replication cluster are used together.
  • 🪲 v13.2.6 PR #3567 Updated manticore-backup dependency to version 1.9.6.
  • 🪲 v13.2.5 PR #3565 Fixed CI setup to improve Docker image compatibility.
  • 🪲 v13.2.4 Fixed handling of long tokens. Some special tokens (like regex patterns) could create words that are too long, so they are now shortened before use.
Loading

Manticore Search 13.2.3

08 Jul 15:40
@sanikolaev sanikolaev
13.2.3
4db790d

Choose a tag to compare

View all tags
Manticore Search 13.2.3

Manticore Search 13.2.3

Released: July 8th 2025

Blogpost: https://manticoresearch.com/blog/manticore-search-13-2-3/

This version focuses on making Vector Search faster, more memory-efficient, and better suited for large-scale data, while also improving compatibility and stability.

Breaking Changes

  • ⚠️ v13.0.0 Updated the KNN library API to support empty float_vector values. This update doesn’t change the data format but does increase the Manticore Search / MCL API version.
  • ⚠️ v12.0.0 PR #3516 Fixed a bug with incorrect source and destination row IDs during KNN index training and building. This update doesn’t change the data format but increases the Manticore Search / MCL API version.
  • ⚠️ v11.0.0 Added support for new KNN vector search features like quantization, rescoring, and oversampling. This version changes the KNN data format and the KNN_DIST() SQL syntax. The new version can read older data, but older versions won't be able to read the new format.

New Features and Improvements

Bug Fixes

Loading

Manticore Search 10.1.0

10 Jun 04:35
@sanikolaev sanikolaev
10.1.0
f2fb1dd

Choose a tag to compare

View all tags
Manticore Search 10.1.0

Manticore Search 10.1.0

Released: June 9th 2025

Blogpost: https://manticoresearch.com/blog/manticore-search-10-1-0/

This version represents an update with new features, one breaking change and numerous stability improvements and bug fixes. The changes focus on enhancing monitoring capabilities, improving search functionality, and fixing various critical issues that affected system stability and performance.

Dockerfile changes

  • Updated base image to Ubuntu Noble for improved security

Breaking Changes

New Features and Improvements

Bug Fixes

Loading

Manticore Search 9.3.2

02 May 12:21
@sanikolaev sanikolaev
9.3.2-readme
d582d09

Choose a tag to compare

View all tags
Manticore Search 9.3.2

Version 9.3.2

Released: May 2nd 2025

This release includes multiple bug fixes and stability improvements, better table usage tracking, and enhancements to memory and resource management.

❤️ Special thanks to @cho-m for fixing build compatibility with Boost 1.88.0 and @benwills for improving documentation around stored_only_fields.

  • 🪲 v9.3.2 Fixed an issue where the "Show Threads" column showed CPU activity as a float instead of a string; also fixed a PyMySQL result set parsing error caused by a wrong data type.

  • 🪲 v9.3.1 Issue #3343 Fixed leftover tmp.spidx files when the optimize process was interrupted.

  • 🆕 v9.3.0 PR #3337 Added a per-table command counter and detailed table usage statistics.

  • 🪲 v9.2.39 Issue #3236 Fix: prevent table damage by removing complex chunk updates. Using wait functions inside the serial worker broke serial processing, which could damage tables.
    Reimplemented autoflush. Removed external polling queue to avoid unnecessary table locks. Added "small table" condition: if the number of documents is below the 'small table limit' (8192) and no Secondary Index (SI) is used, flushing is skipped.

  • 🪲 v9.2.38 Fix: skip creating Secondary Index (SI) for filters using ALL/ANY on string lists, without affecting JSON attributes.

  • 🪲 v9.2.37 Issue #2898 Added backtick support for system tables.

  • 🪲 v9.2.36 Fix: use a placeholder for cluster operations in legacy code. In the parser, we now clearly separate fields for table and cluster names.

  • 🪲 v9.2.35 Fix: crash when unquoting a single '.

  • 🪲 v9.2.34 Issue #3090 Fix: handling of large document IDs (could previously fail to find them).

  • 🪲 v9.2.33 Fix: use unsigned integers for bit vector sizes.

  • 🪲 v9.2.32 Fix: reduce peak memory usage during merge. docid-to-rowid lookups now use 12 bytes per document instead of 16 bytes. Example: 24 GB RAM for 2 billion docs instead of 36 GB.

  • 🪲 v9.2.31 Issue #3238 Fix: incorrect COUNT(*) value in large real-time tables.

  • 🪲 v9.2.30 Fix: undefined behavior when zeroing string attributes.

  • 🪲 v9.2.29 Minor fix: improved a warning text.

  • 🪲 v9.2.28 Issue #3290 Improvement: enhanced indextool --buildidf

  • 🪲 v9.2.27 Issue #3032 With the Kafka integration, you can now create a source for a specific Kafka partition.

  • 🪲 v9.2.26 Issue #3301 Fix: ORDER BY and WHERE on id could cause OOM (Out Of Memory) errors.

  • 🪲 v9.2.25 Issue #3171 Fix: crash caused by segmentation fault when using grouper with multiple JSON attributes on an RT table that has multiple disk chunks

  • 🪲 v9.2.24 Issue #3246 Fix: WHERE string ANY(...) queries failed after RAM chunk flush.

  • 🪲 v9.2.23 PR #518 Minor auto-sharding syntax improvements.

  • 🪲 v9.2.22 Issue #2763 Fix: global idf file was not loaded when using ALTER TABLE.

  • 🪲 v9.2.21 Fix: global idf files can be large. We now release tables sooner to avoid holding unnecessary resources.

  • 🪲 v9.2.20 PR #3277 Improvement: better validatation of sharding options.

  • 🪲 v9.2.19 PR #3275 Fix: build compatibility with Boost 1.88.0.

  • 🪲 v9.2.18 Issue #3228 Fix: crash during distributed table creation (invalid pointer issue).

  • 🪲 v9.2.17 PR #3272 Fix: multiline fuzzy FACET issue.

  • 🪲 v9.2.16 Issue #3063 Fix: bug in distance calculation when using the GEODIST function.

  • 🪲 v9.2.15 Issue #3027 Minor improvement: support for Elastic's query_string filter format.

Loading

Manticore Search 9.2.14

28 Mar 19:46
@sanikolaev sanikolaev
9.2.14
72d3102

Choose a tag to compare

View all tags
Manticore Search 9.2.14

Version 9.2.14

Released: March 28th 2025

Minor changes

  • Commit fe94 Implemented --mockstack flag to calculate recursive operation stack requirements. The new --mockstack mode analyzes and reports the necessary stack sizes for recursive expression evaluation, pttern matching operations, filter processing. Calculated stack requirements are output to console for debugging and optimization purposes.
  • Issue #3058 Enabled boolean_simplify by default.
  • Issue #3172 Added a new config option: searchd.kibana_version_string, which can be useful when using Manticore with specific versions of Kibana or OpenSearch Dashboards that expect a particular Elasticsearch version.
  • Issue #3211 Fixed CALL SUGGEST to work with 2-character words.
  • Issue #490 Improved fuzzy search: previously, it couldn't sometimes find "defghi" when searching for "def ghi" if another matching document existed.
  • ⚠️ BREAKING Issue #3165 Changed _id to id in some HTTP JSON responses for consistency. Make sure to update your app accordingly.
  • ⚠️ BREAKING 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 when the joining node has the same server_id as an existing node in the cluster. 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 to a unique value before attempting to join the cluster. This change updates the replication protocol. 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.

Bugfixes

  • Commit 6fda Fixed a crash caused by losing the scheduler after a wait; now, specific schedulers like serializer are properly restored.
  • Commit c333 Fixed a bug where weights from the right joined table couldn't be used in the ORDER BY clause.
  • Issue #2644 gcc 14.2.0: fixed lower_bound call error with const knn::DocDist_t*&. ❤️ Thank you @Azq2 for the PR.
  • Issue #3018 Fixed an issue with handling uppercase table names during auto-schema inserts.
  • Issue #3119 Fixed a crash when decoding invalid base64 input.
  • Issue #3121 Fixed two related KNN index issues on ALTER: float vectors now keep their original dimensions, and KNN indexes are now properly generated.
  • Issue #3123 Fixed a crash when building a secondary index on an empty JSON column.
  • Issue #3138 Fixed a crash caused by duplicate entries.
  • Issue #3151 Fixed: fuzzy=1 option couldn't be used with ranker or field_weights.
  • Issue #3163 Fixed a bug where SET GLOBAL timezone had no effect.
  • Issue #3181 Fixed an issue where text field values could be lost when using IDs larger than 2^63.
  • Issue #3189 Fixed: UPDATE statements now correctly respect the query_log_min_msec setting.
  • Issue #3247 Fixed a race condition when saving real-time disk chunks that could cause JOIN CLUSTER to fail.
Loading

Manticore Search 7.4.6

28 Feb 14:21
@sanikolaev sanikolaev
7.4.6
bbd5599

Choose a tag to compare

View all tags
Manticore Search 7.4.6

Version 7.4.6

Released: Feb 28th 2025

Major changes

  • Issue #105 - No need to set EXTRA=1 or MCL=1 when running Manticore in Docker anymore.
  • Issue #832 Integration with Kibana for easier and more efficient data visualization.

Minor changes

  • Issue #1727 Fixed floating-point precision differences between arm64 and x86_64.
  • Issue #2995 Implemented performance optimizations for join batching.
  • Issue #3039 Implemented performance optimizations for EstimateValues in histograms.
  • Issue #3099 Added support for Boost 1.87.0. ❤️ Thank you, @cho-m for the PR.
  • Issue #77 Optimized block data reuse when creating filters with multiple values; added min/max to attribute metadata; implemented pre-filtering of filter values based on min/max.

Bugfixes

  • Commit 73ac Fixed handling of expressions in joined queries when attributes from both the left and right tables are used; fixed the index_weights option for the right table.
  • Issue #2915 Using avg() in a SELECT ... JOIN query could lead to incorrect results; this is now fixed.
  • Issue #2996 Fixed an incorrect result set caused by the implicit cutoff when join batching was enabled.
  • Issue #3031 Fixed a crash in the daemon during shutdown when an active chunk merge was in progress.
  • Issue #3037 Fixed an issue where IN(...) could produce incorrect results.
  • Issue #3038 Setting max_iops / max_iosize in version 7.0.0 could degrade indexing performance; this is now fixed.
  • Issue #3042 Fixed a memory leak in the join query cache.
  • Issue #3052 Fixed the handling of query options in joined JSON queries.
  • Issue #3054 Fixed an issue with the ATTACH TABLE command.
  • Issue #3079 Fixed inconsistencies in error messages.
  • Issue #3087 Setting diskchunk_flush_write_timeout=-1 per table did not disable index flushing; this is now fixed.
  • Issue #3088 Resolved duplicate entries after bulk replacing large IDs.
  • Issue #3126 Fixed a daemon crash caused by a full-text query with a single NOT operator and an expression ranker.
  • Issue #3128 Fixed a potential vulnerability in the CJSON library. ❤️ Thank you, @tabudz for the PR.
Loading

Manticore Search 7.0.0

30 Jan 11:40
@sanikolaev sanikolaev
7.0.0
f05d33e

Choose a tag to compare

View all tags
Manticore Search 7.0.0

Version 7.0.0

Released: Jan 30th 2025

📢📢📢Announcement blog post📢📢📢

Major changes

Minor changes

  • ⚠️ BREAKING Issue #1111 Fixed support for global_idf in RT tables. Requires table recreation.
  • ⚠️ BREAKING Issue #2103 Removed Thai characters from internal cjk charset. Update your charset definitions accordingly: if you have cjk,non_cjk and Thai characters are important for you, change it to cjk,thai,non_cjk, or cont,non_cjk, where cont is the new designation for all continuous-script languages (i.e., cjk + thai). Modify existing tables using ALTER TABLE.
  • ⚠️ BREAKING Issue #2458 Incorporated zlib support in Windows packages.
  • ⚠️ BREAKING Issue #2468 CALL SUGGEST / QSUGGEST now compatible with distributed tables. This increases the master/agent protocol version. If you are running Manticore Search in a distributed environment with multiple instances, make sure to first upgrade the agents, then the masters.
  • ⚠️ BREAKING Issue #2889 Changed column name from Name to Variable name for PQ SHOW META.
  • ⚠️ BREAKING Issue #879 Introduced per-table binlog with new options: binlog_common, binlog for create table / alter table. You need to make a clean shutdown of the Manticore instance before upgrading to the new version.
  • ⚠️ BREAKING Issue #1789 Fixed incorrect error message when a node joins a cluster with the wrong replication protocol version. This change updates the replication protocol. 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.
  • ⚠️ BREAKING Issue #2308 Added support for multiple tables in ALTER CLUSTER ADD and DROP. This change also affects the replication protocol. Refer to the previous section for guidance on handling this update.
  • Issue #2997 Fixed dlopen issue on Macos.
  • Commit 4954 Changed the default cutoff for OPTIMIZE TABLE on tables with KNN indexes to improve search performance.
  • Commit cfc8 Added COUNT(DISTINCT) support for ORDER BY in FACET and GROUP BY.
  • Issue #1103 Improved clarity in logging chunk merging.
  • Issue #1130 Added support for DBeaver.
  • Issue #1546 Implemented secondary indexes for POLY2D()/GEOPOLY2D() functions.
  • Issue #1630 HTTP requests now support Content-Encoding: gzip.
  • Issue #1831 Added SHOW LOCKS command.
  • Issue #2187 Allowed Buddy request to daemon to bypass the searchd.max_connections constraint.
  • Issue #2208 Added support for joining tables via the JSON HTTP interface.
  • Issue #2235 Log successfully processed queries via Buddy in their original form.
  • Issue #2249 Added special mode to run mysqldump for replicated tables.
  • Issue #2268 Improved external files renaming on copy for CREATE TABLE and ALTER TABLE statements.
  • Issue #2402 Updated searchd.max_packet_size default to 128MB.
  • Issue #2419 Added support for IDF boost modifier in JSON "match".
  • Issue #2430 Enhanced binlog writing synchronization to prevent errors.
  • Issue #2479 Added support for SHOW TABLE INDEXES command.
  • Issue #2485 Set session metadata for Buddy replies.
  • Issue #2490 Millisecond resolution for aggregations at compatibility endpoints.
  • Issue #2500 Changed error messages for cluster operations when replication fails to start.
  • Issue #2584 New performance metrics in SHOW STATUS: min/max/avg/95th/99th percentile per query type for the last 1, 5, and 15 minutes.
  • Issue #2639 Replaced all instances of index with table in requests and responses.
  • Issue #2643 Added distinct column to HTTP /sql endpoint aggregation results.
  • Issue #268 Implemented autodetection of data types imported from Elasticsearch.
  • Issue #2744 Added collation support for string JSON field comparison expressions.
  • Issue #2752 Added support for ...
Read more
Loading