[
https://issues.apache.org/jira/browse/OAK-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111340#comment-15111340
]
Vikas Saurabh edited comment on OAK-2477 at 1/21/16 10:01 PM:
--------------------------------------------------------------
For suggestions we have 2 type of configs for sugggestions:
{{suggestUpdateFrequencyMinutes, suggestAnalyzed}} (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,
suggestAnalyzed}} into its own config node under index def (say
//indexDef/{{suggestion}}). [~teofili] wdyt?
was (Author: catholicon):
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)
