similar to: [FTS Xapian] RC release

Displaying 20 results from an estimated 6000 matches similar to: "[FTS Xapian] RC release"

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 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 13
2
[FTS Xapian] Beta release
Ok for having a link on the FTS page. PLease clarify what files are necessary to package it as a separate package On 2019-01-13 19:03, Aki Tuomi wrote: > Yes, from compiling point of view it is done. > > Unfortunately what is not done is all the other work involved, such as fixing all the inevitable bugs it has and maintaining it. We do not want, at this moment, take up maintaining
2019 Jan 13
3
[FTS Xapian] Beta release
Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot: > > I tried to combined it, the "autoreconf" errors are solved > > Now, when I type "make install", the lib is not pushed into dovecot > folder, but somewhere in /usr/local/... > > How to adjust this to have it arriving in the proper folder ? > Depends on your system. It mostly a matter of setting
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 13
3
[FTS Xapian] Beta release
You copied your Makefile.am?there. Stephan made you a working version, can you try that? (sorry for dup) Aki -------- Original message --------From: Joan Moreau <jom at grosjo.net> Date: 13/01/2019 21:39 (GMT+02:00) To: Stephan Bosch <stephan at rename-it.nl> Cc: Aki Tuomi <aki.tuomi at open-xchange.com> Subject: Re: [FTS Xapian] Beta release I used the skeleton from Aki :
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
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:
2019 Jan 14
3
[FTS Xapian] Beta release
Hi, I installed and tested your version, but the indexer process crashes reproducible with the following command after about 2000 messages were indexed: doveadm index -u paul at iwascoding.com -q \* Jan 14 09:26:15 mail dovecot: indexer-worker(paul at iwascoding.com)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Mailbox sent: UID 2038: Opened mail because: fts indexing Jan 14 09:26:15 mail
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 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
2
[FTS Xapian] Beta release
The only point here of this fts-xapian is to get rid of solr (because it is just a nightmare to setup) and squat (because it is considere obsolete). I already sent the changed in configure.ac, makefile.am, etc.. in order to include it in the dovecot, and it compiles properly The only remaining point is to push it in hte git (yes, everything is already done) On 2019-01-13 18:45, Aki Tuomi
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 Feb 17
2
[grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15)
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 dovecot wrote: > Hi, > > The rescan() function is a bit badly designed. Currently what you could do what fts-lucene does and: > - Get list of UIDs for all mails in each folder > - If Xapian has UID that
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 Apr 05
2
FTS delays
On Wed, Apr 03, 2019 at 19:02:52 +0800, Joan Moreau via dovecot wrote: > issue seems in the Git version : Which git revision? Before you updated to the broken revision, which revision/version were you running? Can you try it with 5f6e39c50ec79ba8847b2fdb571a9152c71cd1b6 (the commit just before the fts_enforced=body introduction)? That's the only recent fts change. Thanks, Jeff. >
2019 Apr 03
2
FTS delays
On 3 Apr 2019, at 04:30, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > doveadm search -u jom at grosjo.net mailbox inbox text milan Did that search over my list mail and got 83 results, not able to duplicate your issue. What version of dovecot and have you tried to reindex? dovecot-2.3.5.1 here. -- There is a tragic flaw in our precious Constitution, and I don't know
2018 Dec 04
3
[2.3.4] Segmentation faults
Thanks for mySql For Squat vs Solr, Solr does not reach Squat by very far in terms of results : If I setup Solr, and search (via the search in Roundbube or Evolution) for a keyword or part of the keyword, the results are complete non sense. The diference between "search in full body" and "search in fields" does not even work. Solr with Dovecot seems very early beta