search for: fts_backend_xapian_lookup_multi

...ackend_xapian_update_set_build_key, > fts_backend_xapian_update_unset_build_key, > fts_backend_xapian_update_build_more, > fts_backend_xapian_refresh, > fts_backend_xapian_rescan, > fts_backend_xapian_optimize, > fts_backend_default_can_lookup, > fts_backend_xapian_lookup, > fts_backend_xapian_lookup_multi, > fts_backend_xapian_lookup_done > } > }; > > THank you > On 2019-01-05 08:49, Stephan Bosch wrote: >> >> Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: >>> >>> Why not, but please guide me about the core structure (mandatory funcitons, &gt...

Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: > > Why not, but please guide me about the core structure (mandatory > funcitons, etc..) of a typical Dovecot FTS plugin > The Dovecot API documentation is not exhaustive everywhere, but the basics are documented. The remaining questions can be answered by looking at examples found in similar plugins or the relevant API

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, struct fts_multi_result *result) { struct xapian_fts_backend_update_context *ctx = (struct xapian_fts_backend_update_context *)_ctx; int i=0; while(boxes[i]!=NULL) { if(fts_ba...

...ackend_xapian_update_set_build_key, > fts_backend_xapian_update_unset_build_key, > fts_backend_xapian_update_build_more, > fts_backend_xapian_refresh, > fts_backend_xapian_rescan, > fts_backend_xapian_optimize, > fts_backend_default_can_lookup, > fts_backend_xapian_lookup, > fts_backend_xapian_lookup_multi, > fts_backend_xapian_lookup_done > } > }; > > THank you > > On 2019-01-05 08:49, Stephan Bosch wrote: > > Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: > Why not, but please guide me about the core structure (mandatory funcitons, etc..) of a typical Dove...

...ey, >> fts_backend_xapian_update_unset_build_key, >> fts_backend_xapian_update_build_more, >> fts_backend_xapian_refresh, >> fts_backend_xapian_rescan, >> fts_backend_xapian_optimize, >> fts_backend_default_can_lookup, >> fts_backend_xapian_lookup, >> fts_backend_xapian_lookup_multi, >> fts_backend_xapian_lookup_done >> } >> }; >> >> >> THank you >> >> On 2019-01-05 08:49, Stephan Bosch wrote: >> >>> >>> Op?04/01/2019?om?11:17?schreef?Joan?Moreau?via?dovecot: >>>> >>>> Why not, but...

...ly , 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, struct fts_multi_result *result) > { > struct xapian_fts_backend_update_context *ctx = > (struct xapian_fts_backend_update_context *)_ctx; > > int i=0; > &gt...

...ackend_xapian_update_set_build_key, > fts_backend_xapian_update_unset_build_key, > fts_backend_xapian_update_build_more, > fts_backend_xapian_refresh, > fts_backend_xapian_rescan, > fts_backend_xapian_optimize, > fts_backend_default_can_lookup, > fts_backend_xapian_lookup, > fts_backend_xapian_lookup_multi, > fts_backend_xapian_lookup_done > } > }; > > THank you > > On 2019-01-05 08:49, Stephan Bosch wrote: > > Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: > Why not, but please guide me about the core structure (mandatory funcitons, etc..) of a typical Dove...

...fts_backend_xapian_update_expunge, fts_backend_xapian_update_set_build_key, fts_backend_xapian_update_unset_build_key, fts_backend_xapian_update_build_more, fts_backend_xapian_refresh, fts_backend_xapian_rescan, fts_backend_xapian_optimize, fts_backend_default_can_lookup, fts_backend_xapian_lookup, fts_backend_xapian_lookup_multi, fts_backend_xapian_lookup_done } }; THank you On 2019-01-05 08:49, Stephan Bosch wrote: > Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: > >> Why not, but please guide me about the core structure (mandatory funcitons, etc..) of a typical Dovecot FTS plugin > The Dove...

...ackend_xapian_update_set_build_key, > fts_backend_xapian_update_unset_build_key, > fts_backend_xapian_update_build_more, > fts_backend_xapian_refresh, > fts_backend_xapian_rescan, > fts_backend_xapian_optimize, > fts_backend_default_can_lookup, > fts_backend_xapian_lookup, > fts_backend_xapian_lookup_multi, > fts_backend_xapian_lookup_done > } > }; > > THank you > On 2019-01-05 08:49, Stephan Bosch wrote: >> >> Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: >>> >>> Why not, but please guide me about the core structure (mandatory funcitons, &gt...

...ately via lookup() for each folder. With lookup_multi() there can be just one lookup, and the backend can filter only the wanted folders and return them directly. So it's an optimization for FTS indexes that support user-global searches rather than only per-folder searches. >> 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, struct fts_multi_result *result) >> { >> struct xapian_fts_backend_update_context *ctx = >> (struct xapian_fts_backend_update_context *)_ctx; >> >>...

...ackend_xapian_update_set_build_key, > fts_backend_xapian_update_unset_build_key, > fts_backend_xapian_update_build_more, > fts_backend_xapian_refresh, > fts_backend_xapian_rescan, > fts_backend_xapian_optimize, > fts_backend_default_can_lookup, > fts_backend_xapian_lookup, > fts_backend_xapian_lookup_multi, > fts_backend_xapian_lookup_done > } > }; > > THank you > > On 2019-01-05 08:49, Stephan Bosch wrote: > > Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: > Why not, but please guide me about the core structure (mandatory funcitons, etc..) of a typical Dove...

...ackend_xapian_update_set_build_key, > fts_backend_xapian_update_unset_build_key, > fts_backend_xapian_update_build_more, > fts_backend_xapian_refresh, > fts_backend_xapian_rescan, > fts_backend_xapian_optimize, > fts_backend_default_can_lookup, > fts_backend_xapian_lookup, > fts_backend_xapian_lookup_multi, > fts_backend_xapian_lookup_done > } > }; > > THank you > > On 2019-01-05 08:49, Stephan Bosch wrote: > > Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: > Why not, but please guide me about the core structure (mandatory funcitons, etc..) of a typical Dove...

...ackend_xapian_update_set_build_key, > fts_backend_xapian_update_unset_build_key, > fts_backend_xapian_update_build_more, > fts_backend_xapian_refresh, > fts_backend_xapian_rescan, > fts_backend_xapian_optimize, > fts_backend_default_can_lookup, > fts_backend_xapian_lookup, > fts_backend_xapian_lookup_multi, > fts_backend_xapian_lookup_done > } > }; > > THank you > > On 2019-01-05 08:49, Stephan Bosch wrote: > > Op 04/01/2019 om 11:17 schreef Joan Moreau via dovecot: > Why not, but please guide me about the core structure (mandatory funcitons, etc..) of a typical Dove...

...ately via lookup() for each folder. With lookup_multi() there can be just one lookup, and the backend can filter only the wanted folders and return them directly. So it's an optimization for FTS indexes that support user-global searches rather than only per-folder searches. >> 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, struct fts_multi_result *result) >> { >> struct xapian_fts_backend_update_context *ctx = >> (struct xapian_fts_backend_update_context *)_ctx; >> >>...

...return them directly. So </div> <div> it's an optimization for FTS indexes that support user-global searches </div> <div> rather than only per-folder searches. </div> <div> <br> </div> <div> static int fts_backend_xapian_lookup_multi(struct fts_backend *_backend, </div> <div> struct mailbox *const boxes[], struct mail_search_arg *args, enum </div> <div> fts_lookup_flags flags, struct fts_multi_result *result) </div> <div> { </div> <div> stru...

...ately via lookup() for each folder. With lookup_multi() there can be just one lookup, and the backend can filter only the wanted folders and return them directly. So it's an optimization for FTS indexes that support user-global searches rather than only per-folder searches. >> 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, struct fts_multi_result *result) >> { >> struct xapian_fts_backend_update_context *ctx = >> (struct xapian_fts_backend_update_context *)_ctx; >> >>...

...run separately via lookup() for each folder. With lookup_multi() there can be just one lookup, and the backend can filter only the wanted folders and return them directly. So it's an optimization for FTS indexes that support user-global searches rather than only per-folder searches. 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, struct fts_multi_result *result) { struct xapian_fts_backend_update_context *ctx = (struct xapian_fts_backend_update_context *)_ctx; int i=0; while(boxes[i]!=NULL) { if(fts_back...

...lookup_multi() there can be just one lookup, and the >> backend can filter only the wanted folders and return them directly. So >> it's an optimization for FTS indexes that support user-global searches >> rather than only per-folder searches. >> >> 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, struct fts_multi_result *result) >> { >> struct xapian_fts_backend_update_context *ctx = >> (struct xapian_fts_backend_update_context *)_c...

A starting point would be to have a look at the current FTS plugins: https://github.com/dovecot/core/tree/master/src/plugins/fts-solrandhttps://github.com/dovecot/core/tree/master/src/plugins/fts-squat -M Am Freitag, den 04.01.2019, 18:17 +0800 schrieb Joan Moreau via dovecot: > Why not, but please guide me about the core structure (mandatory > funcitons, etc..) of a typical Dovecot FTS

...h > folder. With lookup_multi() there can be just one lookup, and the > backend can filter only the wanted folders and return them directly. So > it's an optimization for FTS indexes that support user-global searches > rather than only per-folder searches. > > 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, struct fts_multi_result *result) > { > struct xapian_fts_backend_update_context *ctx = > (struct xapian_fts_backend_update_context *)_ctx; > > int...