search for: build_more

...indexer first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) > Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? The idea is that it calls something like: - build_key(type=hdr, hdr_name=From) - build_more("tss at iki.fi") - build_key(type=hdr, hdr_name=Subject) - build_more("Re: Solr -> Xapian ?") - build_key(type=body_part) - build_more("message body piece")...

...xer first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) > > Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? > The idea is that it calls something like: > > - build_key(type=hdr, hdr_name=From) > - build_more("tss at iki.fi") > - build_key(type=hdr, hdr_name=Subject) > - build_more("Re: Solr -> Xapian ?") > - build_key(type=body_part) > - build_more...

...ther difficult to keep </div> <div> track of.) </div> <div> <br> </div> <div> Q2 : WHen Indexing an email, the data is not passed by "build_key". Why </div> <div> so ? What is the link with "build_more" ? </div> <div> The idea is that it calls something like: </div> <div> <br> </div> <div> - build_key(type=hdr, hdr_name=From) </div> <div> - build_more(" <a href="mailto:tss@iki.fi&qu...

...first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) > >> Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? > > The idea is that it calls something like: > > - build_key(type=hdr, hdr_name=From) > - build_more("tss at iki.fi") > - build_key(type=hdr, hdr_name=Subject) > - build_more("Re: Solr -> Xapian ?") > - build_key(type=body_part) > - build...

...39;t want to > index this key, it can return FALSE and caller will skip to next key. */ > bool fts_backend_update_set_build_key(struct fts_backend_update_context *ctx, > const struct fts_backend_build_key *key); > > Same file provides outline of what a build_key is. > > "build_more" , > /* Add more content to the index for the currently specified build key. > Non-BODY_PART_BINARY data must contain only full valid UTF-8 characters, > but it doesn't need to be NUL-terminated. size contains the data size in > bytes, not characters. This function may be call...

...gap, indexer first indexes all the missing mails. So the latest UID is supposed to be the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? The idea is that it calls something like: - build_key(type=hdr, hdr_name=From) - build_more("tss at iki.fi") - build_key(type=hdr, hdr_name=Subject) - build_more("Re: Solr -> Xapian ?") - build_key(type=body_part) - build_more("message body piece") -...

.... So the latest UID is supposed to be the greatest UID. >> (Supporting out-of-order indexing would be rather difficult to keep >> track of.) >> >> Q2 : WHen Indexing an email, the data is not passed by "build_key". Why >> so ? What is the link with "build_more" ? >> The idea is that it calls something like: >> >> - build_key(type=hdr, hdr_name=From) >> - build_more(" tss at iki.fi") >> - build_key(type=hdr, hdr_name=Subject) >> - build_more("Re: Solr -> Xapian ?") >> - build_key...

...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 "build_more" ? > > Q3 : Searching/Lookup : THe fheader in which to llok for (must be a least among "cc, to, from, subject, body") is not appearing in the 'struct' data. WHere to find it ? > > Q4 : Refresh : this is very unclear. How come there would not be the &quot...

...'t want to ?? index this key, it can return FALSE and caller will skip to next key. */ bool fts_backend_update_set_build_key(struct fts_backend_update_context *ctx, ??? ??? ??? ??? ????? const struct fts_backend_build_key *key); Same file provides outline of what a build_key is. > "build_more" , /* Add more content to the index for the currently specified build key. ?? Non-BODY_PART_BINARY data must contain only full valid UTF-8 characters, ?? but it doesn't need to be NUL-terminated. size contains the data size in ?? bytes, not characters. This function may be called many...

...> missing mails. So the latest UID is supposed to be the greatest UID. > (Supporting out-of-order indexing would be rather difficult to keep > track of.) > > Q2 : WHen Indexing an email, the data is not passed by "build_key". Why > so ? What is the link with "build_more" ? > The idea is that it calls something like: > > - build_key(type=hdr, hdr_name=From) > - build_more(" tss at iki.fi") > - build_key(type=hdr, hdr_name=Subject) > - build_more("Re: Solr -> Xapian ?") > - build_key(type=body_part) > - bui...

...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 "build_more" ? Q3 : Searching/Lookup : THe fheader in which to llok for (must be a least among "cc, to, from, subject, body") is not appearing in the 'struct' data. WHere to find it ? Q4 : Refresh : this is very unclear. How come there would not be the "latest" view on inde...

...39;t want to > index this key, it can return FALSE and caller will skip to next key. */ > bool fts_backend_update_set_build_key(struct fts_backend_update_context *ctx, > const struct fts_backend_build_key *key); > > Same file provides outline of what a build_key is. > > "build_more" , > /* Add more content to the index for the currently specified build key. > Non-BODY_PART_BINARY data must contain only full valid UTF-8 characters, > but it doesn't need to be NUL-terminated. size contains the data size in > bytes, not characters. This function may be call...

..._get_last_uid, > fts_backend_xapian_update_init, > fts_backend_xapian_update_deinit, > fts_backend_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...

...39;t want to > index this key, it can return FALSE and caller will skip to next key. */ > bool fts_backend_update_set_build_key(struct fts_backend_update_context *ctx, > const struct fts_backend_build_key *key); > > Same file provides outline of what a build_key is. > > "build_more" , > /* Add more content to the index for the currently specified build key. > Non-BODY_PART_BINARY data must contain only full valid UTF-8 characters, > but it doesn't need to be NUL-terminated. size contains the data size in > bytes, not characters. This function may be call...

Anyone willing to explain those functions ? Most notably " get_last_uid" "set_build_key" "build_more" , what is refresh versus rescan ? 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_xa...

...want to > index this key, it can return FALSE and caller will skip to next key. */ > bool fts_backend_update_set_build_key(struct fts_backend_update_context *ctx, > const struct fts_backend_build_key *key); > > Same file provides outline of what a build_key is. > >> "build_more" , > > /* Add more content to the index for the currently specified build key. > Non-BODY_PART_BINARY data must contain only full valid UTF-8 characters, > but it doesn't need to be NUL-terminated. size contains the data size in > bytes, not characters. This function may be...

...39;t want to > index this key, it can return FALSE and caller will skip to next key. */ > bool fts_backend_update_set_build_key(struct fts_backend_update_context *ctx, > const struct fts_backend_build_key *key); > > Same file provides outline of what a build_key is. > > "build_more" , > /* Add more content to the index for the currently specified build key. > Non-BODY_PART_BINARY data must contain only full valid UTF-8 characters, > but it doesn't need to be NUL-terminated. size contains the data size in > bytes, not characters. This function may be call...

...39;t want to > index this key, it can return FALSE and caller will skip to next key. */ > bool fts_backend_update_set_build_key(struct fts_backend_update_context *ctx, > const struct fts_backend_build_key *key); > > Same file provides outline of what a build_key is. > > "build_more" , > /* Add more content to the index for the currently specified build key. > Non-BODY_PART_BINARY data must contain only full valid UTF-8 characters, > but it doesn't need to be NUL-terminated. size contains the data size in > bytes, not characters. This function may be call...

Hi all, Currently I am developing some changes on the solr plugin. I want this plugin indexing also the attachment's content. I have already started to look on plugin's source but I am having some problems understanding how it works. I didn't understood yet what is the plugin's design and how the plugins are called from the core system and I was wondering if anyone could help me