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 sources. I know of one FTS plugin not written by Dovecot developers: https://github.com/atkinsj/fts-elasticsearch If you really wish to do something like this, just go ahead. It will not be a small effort though. As soon as you have concrete questions, we can help you (don't expect rapid responses though). Regards, Stephan.
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 OTHER FLAGS ?
{
fts_backend_xapian_alloc,
fts_backend_xapian_init,
fts_backend_xapian_deinit,
fts_backend_xapian_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: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 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 sources.
>
> I know of one FTS plugin not written by Dovecot developers:
>
> https://github.com/atkinsj/fts-elasticsearch
>
> If you really wish to do something like this, just go ahead. It will not be
a small effort though. As soon as you have concrete questions, we can help you
(don't expect rapid responses though).
>
> Regards,
>
> Stephan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20190105/81e7be01/attachment-0001.html>
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 other flags ? > { > fts_backend_xapian_alloc, > fts_backend_xapian_init, > fts_backend_xapian_deinit, > fts_backend_xapian_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: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 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 sources. >> >> I know of one FTS plugin not written by Dovecot developers: >> >> https://github.com/atkinsj/fts-elasticsearch >> >> If you really wish to do something like this, just go ahead. It will not be >> a small effort though. As soon as you have concrete questions, we can help >> you (don't expect rapid responses though). >> >> Regards, >> >> Stephan.-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20190106/90338fc7/attachment.html>