[OAK-5258] LuceneIndexEditor skips indexing for unknown nodetype due to stale NodeType registry state

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.5.16, 1.6.0
• Component/s: lucene
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 09/Dec/16 13:28
• Updated: 23/Dec/16 04:37
• Resolved: 12/Dec/16 10:23

Description

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

Issue Links

• relates to: OAK-5218 Enable use of hybrid index before first async indexing is done