Manticore Search: recap of 2019

The year is coming to an end and it's time to recap what's happened with Manticore in 2019. Here's what we will remember 2019 for:

Major new features:

  • Percolate queries have been improved a lot and became production-ready. Our clients have been successfully using the new index type in productions for already more than a year
  • Replication for PQ and RT indexes. No more shell scripts and rsyncs with sporadic failures and high replication latency. The replication is now built-in and synchronous
  • In May Manticore Search v3 was released with a new improved index format better suited to large indexes, new kill-lists mode and higher performance
  • Documents storage. No more need to waste RAM to store your original document texts.
  • Auto-id. Generating an id for RT on application's side is in the past. When you don't have it - just omit it and Manticore will generate it automatically. It's extremely important in cases when Manticore is used as the only documents storage, e.g. in case of log management



  • SSL support was added for our HTTP JSON interface. You can now connect to Manticore Search via HTTPS

Interactive courses

More than 20 interactive courses were published on . That's a unique opportunity to learn Manticore Search most important features right in your browser in just minutes with no need to prepare configuration and other things on your side. You don't even need to read the documentation. We believe it's the best way to learn Manticore for those who just start.


The general idea was to make things simpler, so:

  • instead of maintaining a huge charset_table array in most caes you can write just "charset_table=non_cjk"
  • if you deal with Chinese data you can additionally add "charset_table=cjk" and "morphology=icu_chinese" and Chinese texts that normally do not have spaces will be tokenized properly
  • stopwords are now built-in for 50 languages. For English just add "stopwords=en" and you'll be fine

New functions

  • HIGHLIGHT() which makes highlighting as easy as "select highlight() from index where match('your query')"
  • CONCAT() to concatenate any number of strings
  • LAST_INSERT_ID() - an addition to the Auto-id feature which is important when you need to know the id which was just auto generated

New clients and plugins

Merry Christmas and a Happy New Year!

We wish your 2020 to be amazing! We'll do our best to continue with Manticore Search development and support.

Sincerely yours,
Manticore Software team

Leave a Reply


Personal and team training will maximize them performance. 

Custom development

Need cone custom or individual features?

Fill the form and don’t forget to make the description of what you need.

Free config review

There are often optimizations that can be made to a Sphinx / Manticore setup by changing some simple directives in the configuration or making quick changes to an index definition.

Some common mistakes and issues can include:

  • doing main+delta without kill-lists, even if the delta does include updated records found in the main
  • using wildcarding with very short prefix/infix which can hammer performance in some cases
  • disabled (unintentional) seamless rotates and getting stalls on index rotations
  • adding texts as string attributes even if they are not using for any kind of operation (filtering, grouping, sorting) or mandatory to be present in results
  • using deprecated settings 

Having a quick look on the configuration can show issues or potential issues, this is why we want to offer a gift to our growing community!

When uploading your configuration file, we recommend to remove any database credentials first.

We suggest also you give as many possible details about your setup: how big is the data you have, how typical queries look and what issues you experience.

Contact us