[
https://issues.apache.org/jira/browse/OAK-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111391#comment-15111391
]
Vikas Saurabh commented on OAK-2477:
------------------------------------
btw, as discussed offline, we'd want to maintain backward compatibility with
global level config - so the code would read both places although we'd document
the namespaced location as the preferred (or only??) way.
> Move suggester specific config to own configuration node
> --------------------------------------------------------
>
> Key: OAK-2477
> URL: https://issues.apache.org/jira/browse/OAK-2477
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Tommaso Teofili
> Assignee: Vikas Saurabh
> Labels: docs-impacting, technical_debt
> Fix For: 1.4
>
>
> Currently suggester configuration is controlled via properties defined on
> main config / props node but it'd be good if we would have its own place to
> configure the whole suggest feature to not mix up configuration of other
> features / parameters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
