Hi,
I'm working on migrating my v2.3 -> v2.4 configuration.
>From my 2.3 config I have
...
fts flatcurve {
commit_limit = 2000
29 max_term_size = 60
min_term_size = 3
substring_search = yes
}
...
>From reading the current docs' "Configuration Example"
https://doc.dovecot.org/2.4.1/core/plugins/fts_flatcurve.html#configuration-example
that looks OK for v2.4.1 too.
But a config check fails,
doveconf: Fatal: Error in configuration file
/etc/dovecot/conf.d/50-fts.conf line 29: max_term_size: Unknown setting:
max_term_size (fts_max_term_size or fts_flatcurve_max_term_size not found
either.)
There's no mention of "max_term_size" in
https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html
as a change.
It's also NOT listed as a current setting at
https://doc.dovecot.org/2.4.1/core/summaries/settings.html
Checking in code sources
cd dovecot
git checkout release-2.4.1
Switched to branch 'release-2.4.1'
Your branch is up to date with 'origin/release-2.4.1'.
"min_term_size" is in use
grep "min_term_size" *
fts-backend-flatcurve.c: if (size <
ctx->backend->fuser->set->min_term_size)
fts-backend-flatcurve-xapian.cc: * smaller than min_term_size.
Requires libicu in order to correctly handle
fts-backend-flatcurve-xapian.cc: if (len
< fuser->set->min_term_size)
fts-backend-flatcurve-xapian.cc: if (len
< fuser->set->min_term_size)
fts-flatcurve-settings.c: DEF(UINT, min_term_size),
fts-flatcurve-settings.c: .min_term_size = 2,
fts-flatcurve-settings.h: unsigned int min_term_size;
But no trace of "max_term_size" at all from
grep "max_term_size" *
Is "max_term_size" still valid config?
Does code or documentation, or both, need to change?
Or am I misreading the usage?
Thanks,
Dave
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
