Release 2.6.2

Author: adriannuta

README.md

@@ -1,4 +1,4 @@
-![manticoresearch](https://manticoresearch.com/wp-content/uploads/2018/02/manticoresearch.png) 
+[![manticoresearch](https://manticoresearch.com/wp-content/uploads/2018/02/manticoresearch.png)](https://manticoresearch.com)
 
 -----------------
 

doc/manpages.xml

@@ -953,7 +953,7 @@ $ searchd --config /home/myuser/sphinx.conf --status</programlisting>
 
       <refmiscinfo class="manual">Manticore Search</refmiscinfo>
 
-      <refmiscinfo class="version">2.6.1</refmiscinfo>
+      <refmiscinfo class="version">2.6.2</refmiscinfo>
     </refmeta>
 
     <refnamediv>
@@ -1073,7 +1073,7 @@ zoning &gt; zoning </programlisting></para>
 
       <refmiscinfo class="manual">Manticore Search</refmiscinfo>
 
-      <refmiscinfo class="version">2.6.1</refmiscinfo>
+      <refmiscinfo class="version">2.6.2</refmiscinfo>
     </refmeta>
 
     <refnamediv>

docs/conf_options_reference/data_source_configuration_options.rst

@@ -532,7 +532,8 @@ following rows:
 
 then the indexing results would be equivalent to that of adding a new
 text field with a value of ‘red right hand’ to document 1 and ‘mysql
-sphinx’ to document 2.
+sphinx’ to document 2, including the keyword positions inside the field in the order they come from the query.
+If the rows  needs to be in a specific order, that needs to be explicitly defined in the query.
 
 Joined fields are only indexed differently. There are no other
 differences between joined fields and regular text fields.
@@ -542,7 +543,9 @@ the database driver limitations, **ranged queries** can be used. It
 works similar to the ranged queries in the main indexing loop, see :ref:`ranged_queries`.
 The range will be queried for and fetched upfront once, then multiple
 queries with different ``$start`` and ``$end`` substitutions will be run
-to fetch the actual data. When using ``ranged-main-query`` query then omit
+to fetch the actual data. 
+
+When using ``ranged-main-query`` query then omit
 the ``ranged-query`` and it will automatically use the same query
 from :ref:``sql_query_range`` (useful option in complex inheritance setups to
 save having to manually duplicate the same query many times).
@@ -574,7 +577,7 @@ Example:
         tagstext from query; \
         SELECT docid, CONCAT('tag',tagid) FROM tags ORDER BY docid ASC
 
-    sql_joined_field = bigint tag from ranged-query; \
+    sql_joined_field = tag from ranged-query; \
         SELECT id, tag FROM tags WHERE id>=$start AND id<=$end ORDER BY id ASC; \
         SELECT MIN(id), MAX(id) FROM tags
 

docs/conf_options_reference/searchd_program_configuration_options.rst

@@ -269,6 +269,8 @@ process those files. That speeds up snippet extraction when the total
 amount of document data to process is significant (hundreds of
 megabytes).
 
+Up to ``dist_threads`` threads can be created to handle :ref:`CALL PQ <percolate_query_call>` calls.
+
 Example:
 
 

docs/extending.rst

@@ -303,11 +303,8 @@ FUNCTION <create_function_syntax>` statement. It lets you
 specify the return type neatly so there was especially little reason to
 ruin backwards compatibility *and* change the syntax.
 
-Dynamic plugins are supported in `workers =
-threads <workers>` and
-`workers =
-thread_pool <workers>`
-mode only. Multiple plugins (and/or UDFs) may reside in a single library
+Dynamic plugins are supported in threads and thread_pool workers. 
+Multiple plugins (and/or UDFs) may reside in a single library
 file. So you might choose to either put all your project-specific
 plugins in a single common uber-library; or you might choose to have a
 separate library for every UDF and plugin; that is up to you.

docs/installation.rst

@@ -165,7 +165,7 @@ Running Manticore Search in a Docker Container
 
 Docker images of Manticore Search are hosted publicly on Docker Hub at https://hub.docker.com/r/manticoresearch/manticore/.
 
-For more information about using Docker, see the `Docker Docs <https://docs.docker.com/>`.
+For more information about using Docker, see the `Docker Docs <https://docs.docker.com/>`__.
 
 The searchd daemon runs in nodetach mode inside the container. Default configuration includes a simple Real-Time index and listen on the default ports ( 9306 for SphinxQL and 9312 for SphinxAPI).
 

docs/releasenotes.rst

@@ -1,6 +1,31 @@
 Release notes
 =============
 
+Version 2.6.2 GA, 23 February  2018
+-----------------------------------
+
+Improvements
+~~~~~~~~~~~~
+
+* improved :ref:`Percolate Queries <percolate_query>` performance in case of using NOT operator and for batched documents. 
+* :ref:`percolate_query_call` can use multiple threads depending on :ref:`dist_threads`
+* new full-text matching operator NOTNEAR/N
+* LIMIT for SELECT on percolate indexes
+* :ref:`expand_keywords` can accept 'start','exact' (where 'star,exact' has same effect as '1')
+* ranged-main-query for :ref:`joined fields <sql_joined_field>` which  uses the ranged query defined by  sql_query_range
+
+Bugfixes
+~~~~~~~~
+
+* `72dcf66 <https://github.com/manticoresoftware/manticoresearch/commit/72dcf669744e9b7d636dfc213d24df85ab301f6b>`__ fixed crash on searching ram segments; deadlock on save disk chunk with double buffer; deadlock on save disk chunk during optimize
+* `3613714 <https://github.com/manticoresoftware/manticoresearch/commit/36137149a1c3c0893bdda5a28fc7e8244bf2d4ae>`__ fixed indexer crash on xml embeded schema with empty attribute name
+* `48d7e80 <https://github.com/manticoresoftware/manticoresearch/commit/48d7e8001d2a66466ca64577f27ddc5421a67251>`__ fixed erroneous unlinking of not-owned pid-file
+* `a5563a4 <https://github.com/manticoresoftware/manticoresearch/commit/a5563a465ddc59ef71e65f17b68bc33f9700e838>`__ fixed orphaned fifos sometimes left in temp folder
+* `2376e8f <https://github.com/manticoresoftware/manticoresearch/commit/2376e8fc4508944b96959bd10686c6d51f5145e8>`__ fixed empty FACET result set with wrong NULL row
+* `4842b67 <https://github.com/manticoresoftware/manticoresearch/commit/4842b67acdd5da75672db6c08ac563b48577ddd7>`__ fixed broken index lock when running daemon as windows service
+* `be35fee <https://github.com/manticoresoftware/manticoresearch/commit/be35feef54ded59125750916cd211e56108eddae>`__ fixed wrong iconv libs on mac os
+* `83744a9 <https://github.com/manticoresoftware/manticoresearch/commit/83744a977d7837d1d87cd506b88b0e7eb199efe6>`__ fixed wrong count(*)
+
 Version 2.6.1 GA, 26 January  2018
 ----------------------------------
 

docs/searching/multi-queries.rst

@@ -9,7 +9,7 @@ in one go (more formally, one network request).
 Two API methods that implement multi-query mechanism are
 :ref:`AddQuery() <add_query>` and
 :ref:`RunQueries() <run_queries>`. You can also run multiple
-queries with SphinxQL, see `the section called :ref:`multi-statement_queries`. (In fact, regular
+queries with SphinxQL, see  :ref:`multi-statement_queries`. (In fact, regular
 :ref:`Query() <add_query>` call is internally implemented as
 a single AddQuery() call immediately followed by RunQueries() call.)
 AddQuery() captures the current state of all the query settings set by

docs/searching/percolate_query.rst

@@ -103,7 +103,7 @@ Here are default values for the options:
 -  verbose - 0 (disabled), to provide extended info on matching at :ref:`SHOW META <percolate_query_show_meta>`
 -  query - 0 (disabled), to provide all query fields stored, such as query, tags, filters
 
-
+``CALL PQ`` performance is affected by :ref:`dist_threads`.
 
 .. _percolate_query_list:
 

docs/sphinxql_reference/select_syntax.rst

@@ -250,7 +250,7 @@ supports only one filtering condition.
 
 Because of HAVING is implemented as a whole result set
 post-processing, result set for query with HAVING could be less than
-`max_matches`` allows.
+`max_matches` allows.
 
 .. _select_order_by:
 
@@ -346,7 +346,7 @@ Supported options and respectively allowed values are:
 
       The historically default IDF (Inverse Document Frequency) in
       Manticore is equivalent to
-      ``OPTION idf='normalized,tfidf_normalized'``, and those
+      ``OPTION idf='normalized,tfidf_normalized'``, and those
       normalizations may cause several undesired effects.
 
       First, idf=normalized causes keyword penalization. For instance,
@@ -365,7 +365,7 @@ Supported options and respectively allowed values are:
       [word1 \| nonmatchingword2] would assign different weights to the
       exactly same result set, because the IDFs for both “word1” and
       “nonmatchingword2” would be divided by 2.
-      ``OPTION idf=tfidf_unnormalized`` fixes that. Note that BM25,
+      ``OPTION idf='tfidf_unnormalized'`` fixes that. Note that BM25,
       BM25A, BM25F() ranking factors will be scale accordingly once you
       disable this normalization.
 
@@ -374,7 +374,7 @@ Supported options and respectively allowed values are:
       mutually exclusive; and unspecified flags in such a mutually
       exclusive group take their defaults. That means that
       ``OPTION idf=plain`` is equivalent to a complete
-      ``OPTION idf='plain,tfidf_normalized'`` specification.
+      ``OPTION idf='plain,tfidf_normalized'`` specification.
 
    -  ``local_df`` - 0 or 1,automatically sum DFs over all the local
       parts of a distributed index, so that the IDF is consistent (and