[Rt-commit] [rtir] 03/03: Better explain the actual behavior of this option.

[Kevin Falcone]

This is an automated email from the git hooks/post-receive script.

falcone pushed a commit to branch 3.0.0-releng
in repository rtir.

commit 6e91c4ed1d6d90d1de88cf4a773b5590ccaadc15
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Mon Jul 22 18:09:31 2013 -0400

    Better explain the actual behavior of this option.
    
    When introduced in 591dfd0, this option limited the
    Transactions/Attachments we were going to FTS on, which makes sense.
    
    For performance reasons, it was removed from the Custom Field searches
    prior to 2.4.4 in 8807723.  However, that commit didn't fix the docs,
    and it didn't consider that Lookups now act weirdly based on what you're
    searching for.
    
    In [rtir #14427] I lay out the history and possible fixes.  For 3.0.0,
    documentation is the best solution.
---
 etc/RTIR_Config.pm | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/etc/RTIR_Config.pm b/etc/RTIR_Config.pm
index 18feca7..634a76b 100644
--- a/etc/RTIR_Config.pm
+++ b/etc/RTIR_Config.pm
@@ -312,9 +312,10 @@ Set($ReplyString , '');
 
 =item C<$RTIR_OldestRelatedTickets>
 
-Controls how far back, in days, RTIR should look for tickets which
-might contain a specific string, such as an IP address. Sixty
-days by default.
+Controls how far back, in days, RTIR should look for tickets which might
+contain a specific string. This is only used for Content searches,
+searches based on IP or other Custom Fields are not limited by age
+because the current implementation has poor performance.
 
 =cut
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.