search for: body_part_binari

Displaying 9 results from an estimated 9 matches for "body_part_binari".

Did you mean: body_part_binary
2019 Jan 06
2
Solr -> Xapian ?
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 (
2019 Jan 06
2
Solr -> Xapian ?
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
2019 Jan 06
2
Solr -> Xapian ?
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,
2019 Jan 06
0
Solr -> Xapian ?
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 "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
2019 Jan 06
0
Solr -> Xapian ?
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: > 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
2019 Jan 06
0
Solr -> Xapian ?
for fts_backend_xxx_lookup, where is specidifed in which field (to, cc, subject, body, from, all) to lookup ? On 2019-01-06 16:03, Joan Moreau wrote: > 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
2019 Jan 07
0
Solr -> Xapian ?
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". Why so ? What is the link with
2019 Jan 06
3
Solr -> Xapian ?
and finally , for fts_backend_xxxx_lookup_multi, why is that backend dependent ? Would- nt the below function below be the same for any backend ? Waiting fro your feedback on all those questions Thank you JM ----------------- static int fts_backend_xapian_lookup_multi(struct fts_backend *_backend, struct mailbox *const boxes[], struct mail_search_arg *args, enum fts_lookup_flags flags,
2019 Jan 05
2
Solr -> Xapian ?
Anyone willing to explain those functions ? On January 5, 2019 14:23:10 Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > Thank Stephan > I basically need to know the role/description of each of the functions of > the fts_backend: > > struct fts_backend fts_backend_xapian = { > .name = "xapian", > .flags = FTS_BACKEND_FLAG_NORMALIZE_INPUT, -> what