[Rt-commit] rt branch, 4.0/fts-sphinx-doc, created. rt-4.0.1rc1-5-g58dd08c

[Alex Vandiver]

The branch, 4.0/fts-sphinx-doc has been created
        at  58dd08c301900c27d0add164abb79e0026886f1f (commit)

- Log -----------------------------------------------------------------
commit daec23790756d61474a0d15f5945fea366072576
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Wed May 25 17:53:55 2011 -0400

    Mention starting searchd, and note that subsequent indexer runs need --rotate

diff --git a/docs/full_text_indexing.pod b/docs/full_text_indexing.pod
index 2bd577b..167ef62 100644
--- a/docs/full_text_indexing.pod
+++ b/docs/full_text_indexing.pod
@@ -87,16 +87,23 @@ restart your webserver after making these changes.  It will also print a
 sample Sphinx configuration, which should be placed in
 F</etc/sphinx.conf>, or equivalent.
 
-=head2 Updating the index
-
 To fill the index, you will need to run the C<indexer> command-line tool
 provided by Sphinx:
 
     indexer rt
 
-This command should also be run at regular intervals in order to pick up
-new and updated attachments from RT's database.  Failure to do so will
-result in stale data.
+Finally, start the Sphinx search daemon:
+
+    searchd
+
+=head2 Updating the index
+
+To keep the index up-to-date, you will need to run:
+
+    indexer rt --rotate
+
+...at regular intervals in order to pick up new and updated attachments
+from RT's database.  Failure to do so will result in stale data.
 
 =head2 Caveats
 

commit 58dd08c301900c27d0add164abb79e0026886f1f
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Wed May 25 17:54:24 2011 -0400

    Clarify the wording on the MaxMatches failure, and what it takes to update later

diff --git a/docs/full_text_indexing.pod b/docs/full_text_indexing.pod
index 167ef62..41b2449 100644
--- a/docs/full_text_indexing.pod
+++ b/docs/full_text_indexing.pod
@@ -115,13 +115,17 @@ kept in sync.  The default, set during C<rt-setup-fulltext-index>, is
 maximum number of matches is reached but the results returned do not
 match RT's other criteria.
 
-Take, for example, the instance where only three results are returned,
-and tickets 1, 2, 3, 4, and 5 contain the string "target", but only
-ticket 5 is in status "Open".  A search for C<Content LIKE 'target' AND
-Status = 'Open'> may return no results, despite ticket 5 matching those
-criteria, as Sphinx will only return tickets 1, 2, and 3 as possible
-matches.
-
+Take, for example, the instance where Sphinx is configured to return a
+maximum of three results, and tickets 1, 2, 3, 4, and 5 contain the
+string "target", but only ticket 5 is in status "Open".  A search for
+C<Content LIKE 'target' AND Status = 'Open'> may return no results,
+despite ticket 5 matching those criteria, as Sphinx will only return
+tickets 1, 2, and 3 as possible matches.
+
+After index creation, altering C<MaxMatches> in C<RT_SiteConfig.pm> is
+insufficient to adjust this limit; both C<max_matches> in
+F</etc/sphinx.conf> and C<%FullTextSearch>'s C<MaxMatches> in
+C<RT_SiteConfig.pm> must be updated.
 
 =head1 ORACLE
 

-----------------------------------------------------------------------