Displaying 20 results from an estimated 5000 matches similar to: "[FTS Xapian] Beta release"
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 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
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
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 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
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 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 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 Dec 10
2
dovecot full text search
what FTP module should i use instead of squat that is probably no longer
supported or no longer at all?
i want to upgrade my dovecot installation. it currently uses squat but i
found it often crashes on FTS on large mailboxes.
i found "xapian" addon for dovecot but while it works excellent AFTER
database is created, i found it need like 20 or so minutes to index less
than 10GB of
2019 Jan 13
0
[FTS Xapian] Beta release
You need the fts-xapian.c mostly. All the rest comes from automake (unless you decide to use cmake or something else).
I have attached you a skeleton plugin, which should work against dovecot master.
If you experience problems with the skeleton, let us know.
Aki
> On 13 January 2019 at 20:23 Joan Moreau <jom at grosjo.net> wrote:
>
>
> Ok for having a link on the FTS page.
2019 Jan 13
0
[FTS Xapian] Beta release
Hi
Please find attached the beta release of FTS Xapian, with the objective
to replace fts_squat that is being deprecated.
Configuration is exactly the same as for fts_squat:
plugin {
plugin = fts fts_xapian (...)
fts = xapian
fts_autoindex = yes
fts_enforced = yes
fts_xapian = partial=2 full=20
This is installed on my production server, and I will observe it during
the coming days.
I
2019 Dec 10
1
dovecot full text search
> Where do write ops take place?
to the xapian index subdirectory
> Maybe mount that path to a RAM disk rather than looking for anorher solution.
>
not a solution for a problem but workaround
>>
>> Am 10.12.2019 um 15:50 schrieb Wojciech Puchar via dovecot <dovecot at dovecot.org>:
>>
>> ?what FTP module should i use instead of squat that is probably no
2019 Jan 13
0
[FTS Xapian] Beta release
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 and developing yet another FTS plugin as we have plenty of things to do already.
I invite you to setup your own repository and provide this plugin from there, being the
2019 Jan 13
0
[FTS Xapian] Beta release
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 ?
On 2019-01-13 21:01, Tuomi, Aki wrote:
> You copied your Makefile.am there. Stephan made you a working version, can you try that?
>
>
2019 Jan 13
0
[FTS Xapian] Beta release
> On 13 January 2019 at 17:05 Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
>
>
> Hi
>
> Please find attached the beta release of FTS Xapian, with the objective
> to replace fts_squat that is being deprecated.
>
> Configuration is exactly the same as for fts_squat:
>
> plugin {
>
> plugin = fts fts_xapian (...)
> fts = xapian
>
2019 Jan 13
0
[FTS Xapian] Beta release
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
./src/plugins/fts-xapian/Makefile.am
./src/plugins/fts-xapian/fts-backend-xapian-functions.cpp
./src/plugins/fts-xapian/fts-xapian-plugin.c
into src/ directory
2019 Jan 14
0
[FTS Xapian] Beta release
Thank you Stephan.
The version here shall be up and running :
https://github.com/grosjo/fts-xapian
On 2019-01-14 00:07, Stephan Bosch wrote:
> 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
2020 Aug 29
2
lazy_expunge and fts_autoindex
Hi list,
I have both lazy_expunge and fts_autoindex activated (with fts-xapian), as
follows:
plugin {
lazy_expunge = EXPUNGED/
}
plugin {
fts = xapian
fts_xapian = partial=2 full=20 attachments=1 verbose=0
fts_autoindex = yes
fts_enforced = yes
fts_autoindex_exclude = EXPUNGED
fts_autoindex_exclude2 = EXPUNGED/*
}
However, I still see "indexer-worker...: Info: Indexed 1 messages in