similar to: Way to remove FTS indexes

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

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

Hello, Im getting problem on FTS on new created folders (mailboxes). How to simulate: - Enable FTS (solr on our case) - Create a new folder (mailbox) - Move some message to that mailbox - Try to search for the message contents *doveadm search -u user at domain text sometext* # Found nothing, but if i move the message to another mailbox, the search catch the message. # I tried doveadm index

Hi, I'm using Dovecot 2.2.13 with Dovecot Director, Doveadm server and FTS. I want to run doveadm on Director hosts, but Dovecot server on backend hosts reject "fts *" commands. On Dovecot Director hosts: # doveadm fts optimize -u u0001 at example.jp # echo $? 75 # doveadm fts rescan -u u0001 at example.jp # echo $? 75 doveadm index -u u0001 at example.jp INBOX #

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. >

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

On 21 May 2018, at 14.11, kadafax at gmail.com wrote: > > Le 21/05/2018 ? 12:38, Aki Tuomi a ?crit : >> can you try turning on pluign { fts_enforced = yes } and repeat your test? > > Same (wrong) result: > 1. Send an email with "too6Ouka" in the body > > 2. Search against "too6Ouka": > # doveadm search -u username mailbox INBOX body too6Ouka

Hi all, I have recently worked on fts plugin for ElasticSearch. https://github.com/filiphanes/fts-elastic It is forked from fts-elasticsearch as you can see in PR https://github.com/atkinsj/fts-elasticsearch/pull/21 with following changes (maybe some more) - no duplicate json keys in indexed documents, so compatible with ES 7.x - 1 elastic index for all users with routing by username -

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

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

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

Hi, I am currently testing a 2.1 dovecot setup with fts-solr. Search speed is simply amazing. I decided to try to delete and rebuild the solr indexes, but i can't seem to rebuild them thru dovecot. At first, when telnetting to the imap server, the search initially built the index, and then subsequent searches are blazingly fast. 1- I deleted all the solr indexes with the following query:

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

Hi, Looking at the source, it doesn't seem like fts-solr checks for settings changes using fts_index_have_compatible_settings() like fts-lucene does. Is there any special reason for why fts-solr shouldn't also rebuild indexes if settings has changed? /Peter

Hi, While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 segmentation fault while we wanted to rebuild the solr indizes. Problem [1] was encountered while rebuilding the indizes, and now I don't know how many mails/documents are indexed or where it got stuck. [2] and [3] encountered while just playing around, since I did not know of "tokenize" and did not find a

<!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>

On 10/18/20 10:28 PM, Aki Tuomi wrote: > Dovecot FTS tokenization is not done, unless you have `use_libfts` in fts_solr setting, in your case > > fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts changing - fts_solr = url=https://solr.example.com:8984/solr/dovecot/ soft_commit=yes batch_size=250 + fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts

Hello, I'm trying to experiment with Dovecot and Solr server. I have >30k email addresses that I want to index to speed up searching and save IOPS on mail servers. For now - I'm doing some experiments and I'm testing how it is working. I'm thinking about adding one additional server with Solr and configure all mail servers to use that server. I have some questions. 1. I have

I'm reacreating all FTS indices on all my users' INBOX folders: mkdir ~%s/Maildir/lucene-indexes && chown %s:users ~%s/Maildir/lucene-indexes doveadm index -u %s -q INBOX In "ps auxwww" I'm seeing this: tbudkevy 29186 3.7 0.0 6616 3056 ? S 18:11 0:15 dovecot/indexer-worker [tschuetz INBOX] how can a dovecot/indexer-worker actually access the INBOX

On 11/1/20 10:35 AM, John Fawcett wrote: > Yes, getting more data about any potential problem would be useful. > > Just to clarify: I have a fully working search setup for some time now > over various dovecot releases, so no patches needed to get it working. > > My setup does use fts plugin and fts-solr plugin, but it does not use > lib-fts functionality (that has many