search for: get_last_uid

.../ANDs. > >> 2 - for rescan : who is responsible for passing again the new email ? Is >> the Dovecot core sending again all the emails to index ? or the fts >> shall somehow access the mailbox and read all emails ? Wouldn't just be >> saying "delete all index and get_last_uid is now 0" the easy way ? or >> the fts must process all emails (and block the current thread as a >> mailbx maybe quite large) > > The next indexing run is responsible for it. If you return get_last_uid=0, then indexer starts feeding you all mails. So fts backend doesn't...

...ent "subargs" in mail_search_args 2 - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ? or the fts must process all emails (and block the current thread as a mailbx maybe quite large) 3 - for get_last_uid : this uncertainity is very unclear. "If there is a gap, then indexer first indexes all the missing" -> this mean at a certain point,...

...ther combination of OR/ANDs. > 2 - for rescan : who is responsible for passing again the new email ? Is > the Dovecot core sending again all the emails to index ? or the fts > shall somehow access the mailbox and read all emails ? Wouldn't just be > saying "delete all index and get_last_uid is now 0" the easy way ? or > the fts must process all emails (and block the current thread as a > mailbx maybe quite large) > The next indexing run is responsible for it. If you return get_last_uid=0, then indexer starts feeding you all mails. So fts backend doesn't have to know...

...er combination of OR/ANDs. > 2 - for rescan : who is responsible for passing again the new email ? Is > the Dovecot core sending again all the emails to index ? or the fts > shall somehow access the mailbox and read all emails ? Wouldn't just be > saying "delete all index and get_last_uid is now 0" the easy way ? or > the fts must process all emails (and block the current thread as a > mailbx maybe quite large) The next indexing run is responsible for it. If you return get_last_uid=0, then indexer starts feeding you all mails. So fts backend doesn't have to know abou...

...; <br> </div> <div> the Dovecot core sending again all the emails to index ? or the fts </div> <div> shall somehow access the mailbox and read all emails ? Wouldn't just be </div> <div> saying "delete all index and get_last_uid is now 0" the easy way ? or </div> <div> the fts must process all emails (and block the current thread as a </div> <div> mailbx maybe quite large) </div> <div> <br> </div> <div> 3 - for get_last_uid :...

...ther combination of OR/ANDs. > 2 - for rescan : who is responsible for passing again the new email ? Is > the Dovecot core sending again all the emails to index ? or the fts > shall somehow access the mailbox and read all emails ? Wouldn't just be > saying "delete all index and get_last_uid is now 0" the easy way ? or > the fts must process all emails (and block the current thread as a > mailbx maybe quite large) > The next indexing run is responsible for it. If you return get_last_uid=0, then indexer starts feeding you all mails. So fts backend doesn't have to know...

...ther combination of OR/ANDs. > 2 - for rescan : who is responsible for passing again the new email ? Is > the Dovecot core sending again all the emails to index ? or the fts > shall somehow access the mailbox and read all emails ? Wouldn't just be > saying "delete all index and get_last_uid is now 0" the easy way ? or > the fts must process all emails (and block the current thread as a > mailbx maybe quite large) > The next indexing run is responsible for it. If you return get_last_uid=0, then indexer starts feeding you all mails. So fts backend doesn't have to know...

..._init Jan 12 10:33:27 indexer-worker(jom at grosjo.net)<30970><ms9zEnfCOVyHegAA0thIag:8IhwIHfCOVz6eAAA0thIag>: Warning: fts_xapian init (3,25) Jan 12 10:33:27 indexer-worker(jom at grosjo.net)<30970><ms9zEnfCOVyHegAA0thIag:8IhwIHfCOVz6eAAA0thIag>: Warning: fts_backend_xapian_get_last_uid Jan 12 10:33:27 indexer-worker(jom at grosjo.net)<30970><ms9zEnfCOVyHegAA0thIag:8IhwIHfCOVz6eAAA0thIag>: Error: Mailbox XXX: Status lookup failed: Internal error occurred. Refer to server log for more information. [2019-01-12 10:33:27] Jan 12 10:33:27 indexer-worker(jom at grosjo.net)&l...

...e new email ? Is </div> <div> the Dovecot core sending again all the emails to index ? or the fts </div> <div> shall somehow access the mailbox and read all emails ? Wouldn't just be </div> <div> saying "delete all index and get_last_uid is now 0" the easy way ? or </div> <div> the fts must process all emails (and block the current thread as a </div> <div> mailbx maybe quite large) </div> <div> <br> </div> <div> 3 - for get_last_uid :...

...Ok. > > Additional question : > > - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ? or the fts must process all emails (and block the current thread as a mailbx maybe quite large) > > - for get_last_uid : this uncertainity is very unclear. "If there is a gap, then indexer first indexes all the missing" -> this mean at a certain po...

Ok. Additional question : - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ? or the fts must process all emails (and block the current thread as a mailbx maybe quite large) - for get_last_uid : this uncertainity is very unclear. "If there is a gap, then indexer first indexes all the missing" -> this mean at a certain point, index...

...ent "subargs" in mail_search_args 2 - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ? or the fts must process all emails (and block the current thread as a mailbx maybe quite large) 3 - for get_last_uid : this uncertainity is very unclear. "If there is a gap, then indexer first indexes all the missing" -> this mean at a certain point,...

...resent "subargs" in mail_search_args 2 - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ? or the fts must process all emails (and block the current thread as a mailbx maybe quite large) 3 - for get_last_uid : this uncertainity is very unclear. "If there is a gap, then indexer first indexes all the missing" -> this mean at a certain point, ind...

...x it up to do what you need? That seems way easier than trying to create a FTS driver from scratch. michael > On January 7, 2019 at 7:05 AM 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) > > Q2 : WHen Indexing an email, the data is not passed by "buil...

...>> >> 2 - for rescan : who is responsible for passing again the new email ? Is >> the Dovecot core sending again all the emails to index ? or the fts >> shall somehow access the mailbox and read all emails ? Wouldn't just be >> saying "delete all index and get_last_uid is now 0" the easy way ? or >> the fts must process all emails (and block the current thread as a >> mailbx maybe quite large) >> >> 3 - for get_last_uid : this uncertainity is very unclear. "If there is a >> gap, then indexer first indexes all the missi...

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 mails are always supposed to be indexed from the beginning to the last...

...to index . What "key" is that function referring to ? Or is the "key" here the actual email ? > > On 2019-01-06 08:43, Stephan Bosch wrote: > > Op 06/01/2019 om 01:00 schreef Joan Moreau: Anyone willing to explain those functions ? > > Most notably " get_last_uid" > From src/plugins/fts/fts-api.h: > > /* Get the last_uid for the mailbox. */ > int fts_backend_get_last_uid(struct fts_backend *backend, struct mailbox *box, > uint32_t *last_uid_r); > > The solr sources ( src/plugins/fts-solr/fts-backend-solr.c:213) tell me this retu...

Op 06/01/2019 om 01:00 schreef Joan Moreau: > Anyone willing to explain those functions ? > > Most notably " get_last_uid" From src/plugins/fts/fts-api.h: /* Get the last_uid for the mailbox. */ int fts_backend_get_last_uid(struct fts_backend *backend, struct mailbox *box, ??? ??? ??? ???? uint32_t *last_uid_r); The solr sources ( src/plugins/fts-solr/fts-backend-solr.c:213) tell me this returns the last U...

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) Q2 : WHen Indexing an email, the data is not passed by "build_key"....

...to index . What "key" is that function referring to ? Or is the "key" here the actual email ? > > On 2019-01-06 08:43, Stephan Bosch wrote: > > Op 06/01/2019 om 01:00 schreef Joan Moreau: Anyone willing to explain those functions ? > > Most notably " get_last_uid" > From src/plugins/fts/fts-api.h: > > /* Get the last_uid for the mailbox. */ > int fts_backend_get_last_uid(struct fts_backend *backend, struct mailbox *box, > uint32_t *last_uid_r); > > The solr sources ( src/plugins/fts-solr/fts-backend-solr.c:213) tell me this retu...