Xapian/Cyrus/Thunderbird

[Sebastian Hagedorn]

--On 11. Mai 2018 um 13:32:29 +0200 Robert Stepanek <rsto at fastmailteam.com> 
wrote:

> On Fri, May 11, 2018, at 13:04, Sebastian Hagedorn wrote:
>> For my understanding: does that mean the Xapian index is only used for
>> clients that support RFC 6203? If that is the case, how are
>> "traditional"  IMAP searches handled?
>
> For non-FUZZY text SEARCH, Cyrus attempts to match the string on its own
> [1].

That sounds strange to me, because Cyrus 2.4 and earlier don't support 
FUZZY, and there the SQUAT index was used, if present. Only messages that 
were added after the last squatter run were searched directly. Why would 
that have changed?

> Off the top of my head, I don't think Cyrus falls back to the
> search-engine index for large corpus text matches. Using FUZZY always is
> the better choice, but if there's a real-world issue, please let me know.

At this point I can't really say, because our production server still runs 
2.4. I have no idea which clients use FUZZY if it's available, and which 
don't.

> It might be possible to switch to Xapian also for non-FUZZY search.

I think if Xapian only does fuzzy, some searches may be *slower* than using 
a SQUAT index. That seems counterintuitive, at the least. Do you have 
internal search benchmarks? Without metrics it's hard to say if any of this 
actually matters ...
-- 
    .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
                 .:.Regionales Rechenzentrum (RRZK).:.
   .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20180511/c6d484af/attachment-0001.sig>