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:42:38 UTC

[jira] [Resolved] (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 resolved OAK-5894.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

Done with 1785916. Now the {{type}} would be set to {{lucene}} for all cases except its already set to {{disabled}}

> 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.7.0, 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)