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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/03/08 05:21:38 UTC
[jira] [Assigned] (OAK-5894) IndexDefinitionBuilder shouldn't set
type=lucene if type=disabled in existing tree
[ https://issues.apache.org/jira/browse/OAK-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra reassigned OAK-5894:
------------------------------------
Assignee: Chetan Mehrotra
> IndexDefinitionBuilder shouldn't set type=lucene if type=disabled in existing tree
> ----------------------------------------------------------------------------------
>
> Key: OAK-5894
> URL: https://issues.apache.org/jira/browse/OAK-5894
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.8
>
>
> IndexDefinitionBuilder is often used to provision indices in RepositoryInitializer. In current form, provisioning would lead to setting up type="lucene" (and hence reindex=true as a side-effect) even if the definition had been marked disabled.
> Sure, the provisioning logic can do that check - but the behavior of not setting type=lucene sounds like a sane default behavior.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)