search for: fts_backend_xxx_update_expunge

For "rescan " and "optimize", wouldn't it be the dovecot core who indicate which are to be dismissed (expunged), or re-ask for indexing a particular (or all) uid ? WHy would the backend be aware of the transactions on the mailbox ??? There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? On 2019-01-06 15:41, Joan Moreau wrote: > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan Moreau wrote: &g...

...; > For "rescan " and "optimize", wouldn't it be the dovecot core who indicate which are to be dismissed (expunged), or re-ask for indexing a particular (or all) uid ? WHy would the backend be aware of the transactions on the mailbox ??? > > There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? > > On 2019-01-06 15:41, Joan Moreau wrote: > > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan M...

...ow thinking about it, that sounds like a simpler and better way. optimize() is currently done only when explicitly running "doveadm fts optimize", which requests running a slower index optimization. Depends on the FTS backend whether this is useful or not. >> There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? Normally when mails are expunged, update_expunge() is called to notify FTS backend that it should delete the mail also from FTS index. >> .flags = FTS_BACKEND_FLAG_NORMALIZE_INPUT,*-> what other...

...: > For "rescan " and "optimize", wouldn't it be the dovecot core who indicate which are to be dismissed (expunged), or re-ask for indexing a particular (or all) uid ? WHy would the backend be aware of the transactions on the mailbox ??? > > There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? > > On 2019-01-06 15:41, Joan Moreau wrote: > > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan M...

...ow thinking about it, that sounds like a simpler and better way. optimize() is currently done only when explicitly running "doveadm fts optimize", which requests running a slower index optimization. Depends on the FTS backend whether this is useful or not. >> There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? Normally when mails are expunged, update_expunge() is called to notify FTS backend that it should delete the mail also from FTS index. >> .flags = FTS_BACKEND_FLAG_NORMALIZE_INPUT,*-> what other...

...; > For "rescan " and "optimize", wouldn't it be the dovecot core who indicate which are to be dismissed (expunged), or re-ask for indexing a particular (or all) uid ? WHy would the backend be aware of the transactions on the mailbox ??? > > There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? > > On 2019-01-06 15:41, Joan Moreau wrote: > > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan M...

...</div> <div> optimize", which requests running a slower index optimization. Depends </div> <div> on the FTS backend whether this is useful or not. </div> <div> <br> </div> <div> There is alredy "fts_backend_xxx_update_expunge", so I beleive the </div> <div> management of the expunged messages is *NOT* in the backend, right ? </div> <div> Normally when mails are expunged, update_expunge() is called to notify </div> <div> FTS backend that it should del...

...ow thinking about it, that sounds like a simpler and better way. optimize() is currently done only when explicitly running "doveadm fts optimize", which requests running a slower index optimization. Depends on the FTS backend whether this is useful or not. >> There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? Normally when mails are expunged, update_expunge() is called to notify FTS backend that it should delete the mail also from FTS index. >> .flags = FTS_BACKEND_FLAG_NORMALIZE_INPUT,*-> what other...

...n core. Now thinking about it, that sounds like a simpler and better way. optimize() is currently done only when explicitly running "doveadm fts optimize", which requests running a slower index optimization. Depends on the FTS backend whether this is useful or not. There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? Normally when mails are expunged, update_expunge() is called to notify FTS backend that it should delete the mail also from FTS index. .flags = FTS_BACKEND_FLAG_NORMALIZE_INPUT,*-> what other flags ?* Y...

...and better way. >> >> optimize() is currently done only when explicitly running "doveadm fts >> optimize", which requests running a slower index optimization. Depends >> on the FTS backend whether this is useful or not. >> >> There is alredy "fts_backend_xxx_update_expunge", so I beleive the >> management of the expunged messages is *NOT* in the backend, right ? >> Normally when mails are expunged, update_expunge() is called to notify >> FTS backend that it should delete the mail also from FTS index. >> >> .flags = FTS_BACKEND_...

for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > Thank you > > I still don't get the "build_key" function. The email (body, hearders, .. and the uid) is the one (and only) to index . What "key" is that function referring to ? Or is the

...t sounds like a simpler and better way. > > optimize() is currently done only when explicitly running "doveadm fts > optimize", which requests running a slower index optimization. Depends > on the FTS backend whether this is useful or not. > > There is alredy "fts_backend_xxx_update_expunge", so I beleive the > management of the expunged messages is *NOT* in the backend, right ? > Normally when mails are expunged, update_expunge() is called to notify > FTS backend that it should delete the mail also from FTS index. > > .flags = FTS_BACKEND_FLAG_NORMALIZE_INPUT...