Skip to content

Releases: manticoresoftware/docker

Manticore Search 25.0.0

30 Mar 05:05
@sanikolaev sanikolaev
25.0.0
92db3e2

Choose a tag to compare

View all tags
Manticore Search 25.0.0 Latest
Latest

Version 25.0.0

Released: March 30th 2026

This release brings a broader packaging overhaul, new API_URL and API_TIMEOUT options for auto-embedding models, hybrid search, S3-compatible backup and restore support, faster RT tables maintenance with N-way merges and parallel OPTIMIZE, KNN prefiltering, and MySQL-compatible prepared statements.

Breaking Changes

  • ⚠️ v25.0.0 PR #123 Breaking change: updated MCL to 13.0.0, adding API_URL and API_TIMEOUT for auto-embedding models. This affects you if you use auto-embedding models or manage MCL separately from the daemon, because Manticore 25.0.0 requires MCL 13.0.0 and is not compatible with older MCL versions; upgrade the daemon and MCL together, and downgrade is only safe if you also restore a matching older MCL version.
  • ⚠️ v24.0.0 Issue #4343 Breaking change: the internal replication protocol version is bumped, and cluster epoch tracking is added so recovering nodes can detect when cluster table membership changed while they were offline and use SST instead of failing during IST recovery. This affects you only if you use replication clusters: mixed-version replication clusters are not compatible across this change, so upgrade clustered nodes together, and downgrade is only safe before the new replication protocol is used in the cluster.
  • ⚠️ v23.0.0 Issue #4364 Breaking change: index format version 69 is introduced to support new bigram tokenization options, including bigram_delimiter modes and digit-aware bigram_index modes. This affects you if you use those bigram options or if you rebuild indexes and later need to open the rewritten indexes with an older Manticore version: existing older indexes remain readable, but indexes rebuilt or newly written in format 69 are not compatible with older Manticore versions, so downgrade is only safe before such indexes are rewritten.
  • ⚠️ v22.0.0 Issue #4301 Breaking change: embedding generation for RT tables is moved out of the commit phase and replicated as vector data. This affects you if you use replication clusters with RT tables that have model_name: it preserves user-provided vectors, prevents replicas from regenerating different embeddings, and improves auto-embeddings performance when used with replication, but mixed-version replication clusters are not compatible across this change. Upgrade clustered nodes together; downgrade is only safe before the new replication protocol is used in the cluster.
  • ⚠️ v21.0.0 PR #138 Breaking change: updated MCL to 12.0.0 and bumped the required KNN API to support adaptive KNN early termination during HNSW traversal. This affects you if you manage MCL separately from the daemon or run KNN queries that rely on the previous candidate exploration behavior or borderline result selection: Manticore 21.0.0 requires MCL 12.0.0 with the newer KNN interface, and with that library KNN search can stop earlier once enough candidates are found, which may change which candidates are explored and returned. Existing data remains compatible and no special migration is required, but upgrade the daemon and MCL together; downgrade is only safe if you also restore a matching older MCL version.
  • ⚠️ v19.0.0 Issue #4103 Breaking change: added KNN prefiltering. This affects you if you run KNN queries together with attribute filters, because filters can now be applied during KNN search instead of only after candidate selection. That changes result-selection behavior for filtered KNN queries by prioritizing filtered nearest neighbors; no special migration is required, but queries relying on the previous post-filtered result behavior may return different results after upgrade. Downgrade is possible since no index or protocol format change is introduced by this feature.
  • ⚠️ v18.0.0 Issue #4261 Breaking change: index format version 68 is introduced to fix hitless_words dictionary layout handling. This affects you if you rebuild or newly write indexes and later need to open them with an older Manticore version: existing older indexes remain readable, but any indexes rebuilt or newly written in the new format are not compatible with older Manticore versions, so downgrade is only safe before such indexes are rewritten.

Packaging-related changes

  • 🆕 v25.0.0 PR #4357 Packaging change: manticore is now a bundle package for deb and rpm. It includes the daemon, tools, converter, development headers, ICU data, bundled dependency packages (manticore-columnar-lib, manticore-backup, manticore-buddy, manticore-executor, manticore-load, manticore-galera, and manticore-tzdata where applicable), plus built-in language packs for German, English, and Russian, along with Jieba support. The Ukrainian lemmatizer is not bundled; install it separately using the Debian/Ubuntu or RHEL/CentOS instructions.
    When upgrading from the previous package layout, normally you can just install the manticore package. If the old split packages cause conflicts, remove them with apt remove 'manticore*' or yum remove 'manticore*' and then install manticore. That cleanup does not remove your existing data or configuration.

New Features and Improvements

  • 🆕 v24.4.0 PR #4091 Improved RT table compaction by adding N-way disk chunk merges and parallel OPTIMIZE jobs, reducing the time needed to merge many disk chunks and exposing the new merge_chunks_per_job and parallel_chunk_merges settings.
  • 🆕 v24.3.0 PR #133 Updated Manticore Backup to 1.10.0, adding S3-compatible backup and restore support, including AWS S3, MinIO, Wasabi, and Cloudflare R2.
  • 🆕 v24.2.0 Issue #2079 Added hybrid search with Reciprocal Rank Fusion (fusion_method='rrf'), allowing SQL and JSON queries to combine full-text and KNN results, rank them with hybrid_score(), and support multiple KNN subqueries in a single fused result set.
  • 🆕 v24.1.0 PR #141 Updated MCL to 12.4.1, adding support for GGUF quantized local embedding models, T5 encoder models, and gated Hugging Face models via token-authenticated downloads.
  • 🆕 v23.2.0 PR #4372 Updated Buddy to 3.44.0, adding fuzzy search support for queries involving multiple tables.
  • 🆕 v23.1.0 PR #4357 Added a new Manticore bundle package for deb and rpm, replacing the previous meta package to simplify installation and distribution of bundled components.
  • 🆕 v21.1.0 PR #4352 Updated MCL to 12.1.0, improving KNN early-termination performance and adding more efficient 64-bit value encoding.
  • 🆕 [...
Read more
Assets 2
Loading

Manticore Search 17.5.1

07 Feb 12:37
@sanikolaev sanikolaev
17.5.1
c9a317c

Choose a tag to compare

View all tags
Manticore Search 17.5.1

Version 17.5.1

Released: February 7th 2026

Recommended Libraries

  • Recommended MCL version: 10.2.0
  • Recommended Buddy version: 3.41.0

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

❤️ We’d like to thank @pakud for their work on PR #4075.

Breaking Changes

  • ⚠️ v17.0.0 Issue #4120 MCL 10.0.0: Added support for DROP CACHE. This updates the interface between the daemon and MCL. Older Manticore Search versions don't suport the newer MCL.
  • ⚠️ v16.0.0 Issue #4019 Percolate query JSON responses now return hit _id and _score as numbers instead of strings, matching regular search; this is a breaking change for clients that relied on string type for these fields.

New Features and Improvements

  • 🆕 v17.5.0 PR #130 MCL updated to 10.2.0: QWEN model support fixed and support for additional models added.
  • 🆕 v17.3.0 PR #4186 Executor updated to 1.4.0, including an updated PHP version and the llm-php-ext extension.
  • 🆕 v17.2.0 PR #4195 Updated MCL to 10.1.0; Added support for Qwen local embeddings models.
  • 🆕 v17.1.0 Issue #3826 Jieba morphology instances are now shared across tables with the same configuration (mode, HMM flag, user dict path), greatly reducing memory use when many tables use Jieba (e.g. many empty tables no longer cause ~20 GB usage).
  • 🆕 v17.0.7 Issue #2046 In RT mode, stopwords, wordforms, exceptions, and hitless_words can be set inline in CREATE TABLE (semicolon-separated values; wordforms/exceptions use > or => for pairs, with \ escaping), so tables can be created without external files; SHOW CREATE TABLE returns these inline values.
  • 🆕 v16.3.0 KNN search now defaults to oversampling=3 and rescore=1, and supports omitting k so the query limit is used as the effective k; this reduces unnecessary oversampling and improves behavior when using SELECT * with KNN on columnar tables.
  • 🆕 v16.2.0 PR #4088 Added searchd --quiet (-q) flag to suppress startup output (banner and precache messages), printing only errors; useful when starting and stopping searchd in a loop or from scripts.
  • 🆕 v16.0.1 Issue #3336 HTTP connections are now persistent by default when using HTTP/1.1: clients no longer need to send the Keep-Alive header explicitly, reducing random connection failures in API clients (e.g. PHP, Go). To close a connection, the client sends Connection: close. HTTP/1.0 still requires Connection: keep-alive for persistence.

Bug Fixes

  • 🪲 v17.5.1 Issue #3498 Fixed JOIN results returning empty or duplicated values when a column was both a string attribute and a stored field; the attribute value is now returned correctly.
  • 🪲 v17.4.2 Issue #2559 Fixed joins on JSON string attributes (e.g. j.s) returning no matches; they now work like joins on plain string attributes.
  • 🪲 v17.4.1 Fixed stored attributes not being evaluated in final when cutoff is set.
  • 🪲 v17.2.10 Issue #425 Auto table creation (auto schema) now runs for REPLACE INTO as well as INSERT INTO, so tables are created on demand when missing.
  • 🪲 v17.2.9 Issue #3226 Fixed incorrect GROUP BY results on columnar MVA with multiple GROUP BY columns by rejecting such queries with the same error as rowwise ("MVA values can't be used in multiple group-by").
  • 🪲 v17.2.7 Issue #1737 Fixed highlight() with html_strip_mode=strip corrupting content by decoding entities and altering tags; original entity form is now preserved in the highlighted output.
  • 🪲 v17.2.6 Issue #3203 Fixed ALTER TABLE REBUILD SECONDARY failing with failed to rename … .tmp.spjidx when the table had multiple disk chunks.
  • 🪲 v17.2.5 Issue #3226 Fixed incorrect GROUP BY results on columnar MVA with multiple GROUP BY columns by rejecting such queries with the same error as rowwise ("MVA values can't be used in multiple group-by").
  • 🪲 v17.2.4 Issue #4148 Fixed distributed queries returning stored fields from the wrong local index when agent tables contain duplicate document IDs; stored fields now follow index order and the first matching index is used for duplicates.
  • 🪲 v17.2.3 Issue #4176 Fixed table rename breaking tables that use external stopwords, wordforms, or exceptions: ATTACH TABLE now migrates these files to the new chunk-based format and updates disk chunk headers, so after ALTER TABLE RENAME the daemon no longer reports missing external files on restart.
  • 🪲 v17.2.2 Issue #1065 Added the expand_blended search option so that query tokenization applies the table's blend rules and expands blended variants (e.g. "well-being" → "well-being" | "wellbeing" | "well" "being"), allowing one query to match documents indexed with any of those forms.
  • 🪲 v17.1.3 Issue #1618 Bumped Buddy to 3.40.7. Support for using Manticore with HikariCP and JPA/MyBatis (Spring Boot) is provided via Manticore Buddy, which implements the required MySQL wire protocol behavior.
  • 🪲 v17.1.2 Issue #4128 Fixed MATCH with OR over the same phrase in different fields (e.g. (@name ="^New York$") | (@ascii_name ="^New York$")) returning matches from other fields; boolean simplification no longer drops field restrictions in that case.
  • 🪲 v17.1.1 Issue #4131 Fixed ALTER TABLE with table-level settings (e.g. html_strip='1') failing on tables with auto-embeddings with "knn_dims can't be used together with model_name"; serialization now omits knn_dims when model_name is set.
  • 🪲 v17.0.12 PR #4188 Fixed incorrect filter and filter tree evaluation in joined queries.
  • 🪲 v17.0.11 Issue #3661 Fixed intermittent crashes when using columnar MVA64 attributes (e.g. during merge/optimize or when selecting stored/columnar attributes), by correcting docstore and blob-pool handling of columnar MVA64 data.
  • 🪲 v17.0.10 Issue #3944 HIGHLIGHT and snippet generation now support REGEX in the query string, so REGEX matches are highlighted correctly when the same REGEX query is used in MATCH and HIGHLIGHT.
  • 🪲 [v17....
Read more
Loading

Manticore Search 15.1.0

07 Dec 16:40
@sanikolaev sanikolaev
15.1.0
7b6c007

Choose a tag to compare

View all tags
Manticore Search 15.1.0

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](https://github.com/manticoresoftwa...
Read more
Loading

Manticore Search 14.1.0

07 Nov 16:14
@sanikolaev sanikolaev
14.1.0
3056c6b

Choose a tag to compare

View all tags
Manticore Search 14.1.0

Version 14.1.0

Released: November 7th 2025

❤️ We’d like to extend our heartfelt thanks to @ricardopintottrdata for their work on PR #3792 and PR #3828 — addressing issues around HAVING total counts and the filter with empty name error, to @jdelStrother for their contribution with PR #3819, which improves handling of ParseCJKSegmentation when Jieba support isn’t available — and to @ramir1 for PR #121 to the official Docker image to enable the Ukrainian Lemmatizer by default.

Your efforts help make the project stronger — many thanks!

Recommended libraries

  • Recommended MCL version: 8.1.0
  • Recommended Buddy version: 3.37.0

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

⚠️ Important

Version v14.0.0 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.

New Features and Improvements

Bug Fixes

Loading

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

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.
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