Manticore Search 2.7.5 GA release

We are pleased to announce the release of Manticore Search 2.7.5 GA.

Prebuilt packages available for Debian,Ubuntu, Red Hat/CentOS, Windows and OSX can be downloaded from here.

Improvements

  • REGEX function for strings. It can be used on string attributes, string JSON properties or string expressions
  • “limit” and “offset” for JSON API search
  • profiler output time spent on query cache stages

Fixes

A number of bugs have been fixed in this release.

In particular, implicit group ( by using COUNT(*) in SELECT)  in a query  with FACETs  is  not lost anymore. If COUNT(*) is present in SELECT, the main result set will be the same as if the query would not have the FACETs.  Before this fix, the FACETs caused the implicit grouping to be ignored in the main result set.

For a full report please consult the Release note.

 

 

Leave a Reply

Training

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