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 2016/12/12 09:52:58 UTC
[jira] [Reopened] (OAK-5258) LuceneIndexEditor skips indexing for
unknown nodetype due to stale NodeType registry state
[ https://issues.apache.org/jira/browse/OAK-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra reopened OAK-5258:
----------------------------------
> LuceneIndexEditor skips indexing for unknown nodetype due to stale NodeType registry state
> ------------------------------------------------------------------------------------------
>
> Key: OAK-5258
> URL: https://issues.apache.org/jira/browse/OAK-5258
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.6, 1.5.16
>
>
> With OAK-5218 hybrid index can be used since very starting of system. Currently LuceneIndexEditorProvider uses a cached IndexDefinition instance for sync/nrt mode.
> In some cases it can happen that indexed content uses a new nodetype and IndexDefinition which is cached in IndexTracker has yet not updated the cached index definition. This is not a problem with async indexing mode as by the time async indexer kicks in it constructs the IndexDefinition from the current root. However with sync/nrt indexing it posses a problem as nodetype state stored in cached index definition may be old and does not have entry for newly registered nodetypes
> As a fix we should check if NodeType registry state has changed for current root wrt root referred to in IndexDefinition. If changed then cached IndexDefinition should not be used
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)