You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/01/22 16:39:40 UTC

[jira] [Resolved] (OAK-2477) Move suggester specific config to own configuration node

     [ https://issues.apache.org/jira/browse/OAK-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Saurabh resolved OAK-2477.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.4)
                   1.3.15

Implemented on trunk at [r1726237|http://svn.apache.org/r1726237].

Note that the old location is still respected although the new location would be preferred. I'd update the documentation accordingly.

> 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.3.15
>
>         Attachments: OAK-2477.patch
>
>
> 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)