From: Rainer M Krug <Rainer@krugs.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: blog post on gnus, dovecot, and lucene
Date: Thu, 09 Oct 2014 10:30:53 +0200 [thread overview]
Message-ID: <m2a955ve4i.fsf@krugs.de> (raw)
In-Reply-To: <87tx3dtzx5.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 09 Oct 2014 16:23:02 +0800")
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Vincent Bernat <bernat@luffy.cx> writes:
>
>> ❦ 8 octobre 2014 22:15 +0800, Eric Abrahamsen <eric@ericabrahamsen.net> :
>>
>>>> I didn't notice that. I added that to my dovecot.conf:
>>>>
>>>> plugin {
>>>> fts = lucene
>>>> fts_lucene = whitespace_chars=@.
>>>> }
>>>>
>>>> And the search became faster. However, I usually don't use FTS (only
>>>> search on recipient or title). If I check right now, I notice that the
>>>> indexes are not up-to-date. So, you may be right.
>>>
>>> But it's pretty interesting that that did something -- I wasn't sure
>>> that calling dovecot as a process would even invoke the configuration
>>> files at all. But you don't think the indexes were updated, huh?
>>>
>>> It might be worth amending the blog post at some point. I've asked about
>>> this stuff on the dovecot mailing list, but no one seemed to know.
>>
>> I have done a doveadm fts rescan to get those indexes updated. So, maybe
>> the solution could be a cronjob?
Instead of a cronjob, one could run it after the sync with offlinesync
(I am sure mbsync can do it as well) as a hook which is executed
automatically. But there is still the issue of updating after moving
messages from gnus.
>
> Right, that should work fine. At that point, though, I'm inclined just
> to have dovecot run as a daemon...
I think the daemon is the better way to do it.
Cheers,
Rainer
>
>
>
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2014-10-09 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 5:43 Eric Abrahamsen
2014-10-07 5:51 ` Igor Sosa Mayor
2014-10-07 11:14 ` Feng Shu
2014-10-07 11:59 ` Rasmus
2014-10-07 10:09 ` Vincent Bernat
2014-10-07 16:30 ` Eric Abrahamsen
2014-10-08 5:12 ` Vincent Bernat
2014-10-08 14:15 ` Eric Abrahamsen
2014-10-09 5:30 ` Vincent Bernat
2014-10-09 8:23 ` Eric Abrahamsen
2014-10-09 8:30 ` Rainer M Krug [this message]
[not found] ` <m2oatos5yt.fsf@krugs.de>
2014-10-07 16:47 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a955ve4i.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).