search for: fts_backend_xapian_lookup

Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue. > On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote: > > For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox...

...: Query : ( bcc:inbox OR body:inbox OR cc:inbox OR from:inbox OR message-id:inbox OR subject:inbox OR to:inbox OR uid:inbox ) AND ( bcc:milan OR body:milan OR cc:milan OR from:milan OR message-id:milan OR subject:milan OR to:milan OR uid:milan ) > > 1 - The query is wrong That's because fts_backend_xapian_lookup() isn't anywhere close to being correct. Try to copy the logic based on solr_add_definite_query_args().

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

...this. (would it be buggy or no) PLease, have a look deeper And the loop is a very big problem as it times out all the time (and once again, this is not in any of the backend functions) On 2019-04-21 10:42, Timo Sirainen via dovecot wrote: > Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue. > > On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote: > > For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments !...

...a look deeper > > And the loop is a very big problem as it times out all the time (and once again, this is not in any of the backend functions) > > > > > On 2019-04-21 10:42, Timo Sirainen via dovecot wrote: > >> Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue. >> >>> On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net <mailto:jom at grosjo.net>> wrote: >>> >>> For this first point, the problem is that dovecot core sends TWICE the reques...

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

...apian_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 (mandato...

...ts_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: >&...

...o) > > PLease, have a look deeper > > And the loop is a very big problem as it times out all the time (and once again, this is not in any of the backend functions) > > On 2019-04-21 10:42, Timo Sirainen via dovecot wrote: > Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue. > > On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote: > > For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments !...

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

...apian_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 (mandato...

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

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

...box OR body:inbox OR cc:inbox OR from:inbox OR message-id:inbox OR subject:inbox OR to:inbox OR uid:inbox ) AND ( bcc:milan OR body:milan OR cc:milan OR from:milan OR message-id:milan OR subject:milan OR to:milan OR uid:milan ) >> >> 1 - The query is wrong > > That's because fts_backend_xapian_lookup() isn't anywhere close to being correct. Try to copy the logic based on solr_add_definite_query_args(). -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20190421/453f773a/attachment.html>

...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; >> &gt...

...apian_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 (mandato...

...apian_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 (mandato...

...apian_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 (mandato...

...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; >> &gt...