Displaying 20 results from an estimated 9000 matches similar to: "[grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15)"
2019 Feb 08
2
Fwd: [grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15)
Hi,
THis is a core problem in Dovecot in my understanding.
In my opinion, the rescan in dovecot should send to the FTS plugin the
list of "supposedly" indexed emails (UID), and the plugin shall purge
the redundant UID (i..e UID present in the index but not in the list
sent by dovecot) and send back the list of UID not in its indexes to
dovecot, so Dovect can send one by one the
2019 Feb 17
0
[grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15)
Not really, as the steps outlined by Timo would not get done.
Aki
> On 17 February 2019 at 10:56 Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
>
>
> In such case, as long as the API is not upgraded, should
>
> doveadm index -A -q \*
>
> be considered a replacement of
>
> doveadm fts rescan
>
> On 2019-02-14 16:24, Timo Sirainen via
2019 Apr 05
2
FTS delays
On Fri, Apr 05, 2019 at 19:33:57 +0800, Joan Moreau via dovecot wrote:
> Hi
>
> If you plan to fix the FTS part of Dovecot, I will be very gratefull.
I'm trying to figure out what is causing the 3rd issue you listed, so we can
decide how severe it is and therefore how quickly it needs to be fixed. At
the moment we are unable to reproduce it, and therefore we cannot fix it.
>
2019 Apr 14
2
FTS delays
I have tried to spend some time of understanding the logic (if any !) of
the fts part
Honestly, the one who created this mess shall be the one to fix it, or
one shall refactor it totally.
Basically, the fts "core" should be able to do
- select the backend according to conf file
- send new emails/maiblox to backend
- send teh ID of the emails to be removed
- resend an entire
2019 Apr 05
2
FTS delays
On Fri, Apr 05, 2019 at 17:45:36 +0800, Joan Moreau wrote:
> I am on master (very latest)
>
> No clue exactly when this problem appears, but
>
> 1 - the "request twice the fts plugin instead of once" issue has always
> been there (since my first RC release of fts-xapian)
Ok, good to know.
> 2 - the body/text loop has appeared recently (maybe during the month
2019 Jan 08
3
Solr -> Xapian ?
On 7 Jan 2019, at 16.05, Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
>
> Hi
>
> ANyone to answer specifically ?
>
> Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance)
All the
2019 Jan 12
2
[FTS Xapian] Status & Questions
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Did you remember to load fts first?
</div>
<div>
<br>
</div>
<div>
mail_plugins =$mail_plugins fts fts_xapian
</div>
<div>
<br>
</div>
<div>
Aki
</div>
2012 Oct 16
2
Difference between Indexing and Rescan in FTS
I've had squat running on dovecot 2.0 and have been updating all users
mailbox indexes nighty via cron with this command:
doveadm -v search -A text xyzzyx
I've just updated to 2.1 and I'm migrating to lucene indexes, but reading
the documentation I'm having a hard time understanding the semantic
differences between indexing and rescanning.
If I were to continue to run an
2019 Apr 21
2
FTS delays
Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue.
> On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote:
>
> For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox shall serve to select teh
2019 Apr 21
2
FTS delays
It's because you're misunderstanding how the lookup() function works. It gets ALL the search parameters, including the "mailbox inbox". This is intentional, and not a bug. Two reasons being:
1) The FTS plugin in theory could support indexing/searching any kinds of searches, not just regular word searches. So I didn't want to limit it unnecessarily.
2) Especially with
2019 Jan 13
1
[FTS Xapian] Beta release
Please kindly check https://github.com/grosjo/fts-xapian
On 2019-01-13 20:11, Aki Tuomi wrote:
> If you had looked at what I sent, you'd seen it's quite different from what you sent.
>
> Anyways, put the contents of skeleton.tar.gz and
>
> ./src/plugins/fts-xapian/fts-xapian-plugin.h
> ./src/plugins/fts-xapian/fts-backend-xapian.cpp
>
2019 Jan 14
2
[FTS Xapian] Beta release
Op 14-1-2019 om 13:40 schreef Aki Tuomi:
>
> Just to remind that now that there is a github repo for fts-xapian,
> you could maybe open these issues there instead?
>
Although README.md currently says:
"Please feel free to send your questions, together with the dovecot log
file, to jom at grosjo.net <mailto:jom at grosjo.net> or to the dovecot ML
dovecot at dovecot.org
2015 Oct 13
1
fts solr ignores new mailboxes until fts rescan
Hi Christian,
may be the issue is related to this other post:
http://dovecot.org/pipermail/dovecot/2015-September/102094.html
Anyway, what I can tell you is that for every? user account,? for every
folders created after the last doveadm fts rescan for that user, dovecot
does not invoke indexer.
A new rescan fix the problem for all the folders created up to that moment.
I was wondering if I was
2019 Jan 14
2
[FTS Xapian] Beta release
Here it is:
Jan 14 09:26:08 mail dovecot: indexer-worker(paul at iwascoding.com <mailto:paul at iwascoding.com>)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Effective uid=8, gid=8, home=/var/spool/mail/iwascoding/paul
Jan 14 09:26:08 mail dovecot: indexer-worker(paul at iwascoding.com <mailto:paul at iwascoding.com>)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Quota
2019 Jan 13
2
[FTS Xapian] Beta release
THis is already what I send earlier (see : dovecot-xapian-1.0b2.tar.gz
[1] )
What I would need is the files so one can download (git) it, and type
some command (make ?) to compile it and place it in the right forlder
(/usr/lib/dovecot/ or whatever is configured in the installed dovecot,
which may differ from distribution to distribution)
On 2019-01-13 19:47, Aki Tuomi wrote:
> You need
2019 Jan 14
3
[FTS Xapian] Beta release
Testing a compile on FreeBSD.
gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src'
/bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I.
-I.. -I/opt/dovecot2.3/include/dovecot
-I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD
-MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo
fts-backend-xapian.cpp
libtool:
2015 Oct 12
2
fts solr ignores new mailboxes until fts rescan
Hello,
on my debian wheezy installation, I implemented fts plugin with solr as
indexing system.
I noticed that if a user creates a new folder, that folder it is ignored by
dovecot indexing until a doveadm fts rescan is performed for that user.
From that time on everything works ok on that folder.
As a test I set fts_autoindex=yes and put in that folder a brand new mail
never indexed before. in
2019 Jul 04
2
solr vs fts
Am Donnerstag, den 04.07.2019, 12:27 +0300 schrieb Aki Tuomi via
dovecot:
> On 4.7.2019 12.22, Maciej Milaszewski IQ PL via dovecot wrote:
> > Hi
> > So you're advised to use a solr or something else?
> >
>
> Using any FTS is advisable, currently suitable ones would be SOLR or
> Xapian (see https://github.com/grosjo/fts-xapian)
>
Hi Aki,
I didn't yet
2019 Jan 14
2
[FTS Xapian] Beta release
In your README.md, perhaps "This project intends to provide a
straightforward and simple *procedure *to configure FTS plugin for Dovecot,
leveraging the efforts by the Xapian.org team." is better??
Also in the part after cloning from git:
./configure --prefix=/usr --with-dovecot=/path/to/dovecot [ This
/path/to/dovecot is not obvious. Is it the dovecot binary or what??]
On Mon, 14 Jan
2019 Jan 24
2
[FTS Xapian] RC release
Hi,
FTS Xapian matches my targets for the plugins (replacing deprecated
fts-squat in a production environment)
https://github.com/grosjo/fts-xapian
Please do not hesitate to add "issues" on github, if the case happen
Hope it helps
JM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: