[OAK-2203] Full reindexing is triggered when the IndexEditor is missing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.1.0, 1.1.1
• Fix Version/s: 1.0.8, 1.1.2
• Component/s: core, lucene, solr
• Assignee: Alex Deparvu
• Reporter: Alex Deparvu
• Created: 16/Oct/14 09:07
• Updated: 20/Apr/15 07:30
• Resolved: 23/Oct/14 10:10

Description

Currently the IndexUpdate class responsible for handling the index editors is a bit eager in triggering a reindex in the case where is doesn't find the editor for a specific index type [0].
This has a few drawbacks:

• if you update a bundle with an index impl (ex: oak-lucene) IndexUpdate will catch that downtime, see the index as offline and ask for a reindex. not cool.
• it will eagerly set 'reindex=true' even on nodes that are not index definitions, causing mild annoyances (OAK-2024).

This begs the question: when should we automatically mark for reindex an index definition?

[0] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/IndexUpdate.java#L162

Issue Links

• relates to: OAK-2024 Error when accessing /oak:index/rep:policy/reindex property via JCR