In May 2017 we made a fork of Sphinxsearch 2.3.2, which we called Manticore Search. Below you will find a brief report on Manticore Search as a fork of Sphinx and our achievements since then. Why did we fork Sphinx? First of all, why did we do the fork? At the end of 2016, Read more about Manticore Search: 3 years after forking from Sphinx[…]
About new Manticore Real-Time mode
This article describes one of the ways to do word completion in Manticore Search. What is Autocomplete? Autocomplete (or word completion) is a feature which allows an application to predict the rest of a word while a user is typing it. How it usually works is: the user starts typing a word in the search Read more about Simple autocomplete with Manticore[…]
Starting from v 3.2.0 Manticore Search introduced a new feature - Document Storage.
Historically Manticore Search was a text search engine which indexes texts but doesn't keep the originals. A text is processed, transforming it from a plain string into special structures that form the full-text index, which allows fast text searching. In the result set, the user wasn't receiving the original text, as recomposing it from the full-text index can be a complex process. In addition, indexation settings may include clauses that stop certain words from being indexed (like minimum word length or stopwords) which can make the reconstruction impossible.
In this article we discuss the differences between using SphinxSE and FEDERATED engine with Manticore Search
The SphinxSE MySQL plugin was made available since the first public release of Sphinx Search. The idea was to allow users to perform search queries using the same MySQL connection. Another benefit was the search result could be joined with another MySQL table for further filtering/sorting or to display data not available in the search result. Also at that time SphinxQL didn't exist yet.