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/21 22:37:40 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15111340#comment-15111340 ]
Vikas Saurabh commented on OAK-2477:
------------------------------------
For suggestions we have 2 config: {{suggestUpdateFrequencyMinutes}} (currently gets defined at index def node) and {{useInSuggest}} (set on each property def which should participate in suggestions dictionary).
Had a chat with [~chetanm] and it seems that having {{useInSuggest}} is useful... so, we might just want to namespace {{suggestUpdateFrequencyMinutes}} into its own config node under index def (say //indexDef/{{suggestion}}). [~teofili] wdyt?
> 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)