[OAK-6535] Synchronous Lucene Property Indexes

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.12, 1.8.0
• Component/s: lucene, property-index
• Sprint: L15
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 09/Aug/17 06:41
• Updated: 18/Aug/20 07:14
• Resolved: 07/Nov/17 13:14

Description

Oak 1.6 added support for Lucene Hybrid Index (OAK-4412). That enables near real time (NRT) support for Lucene based indexes. It also had a limited support for sync indexes. This feature aims to improve that to next level and enable support for sync property indexes.

More details at https://wiki.apache.org/jackrabbit/Synchronous%20Lucene%20Property%20Indexes

Issue Links

• duplicates: OAK-4638 Mostly async unique index (for UUIDs for example)
• is related to: OAK-9165 Lucene: unique sync property index don't work properly
• relates to: OAK-4412 Lucene hybrid index
• relates to: OAK-6820 Implement support for disabling indexes which are replaced with newer index
• relates to: OAK-4638 Mostly async unique index (for UUIDs for example)
• relates to: OAK-6574 Lucene index: include/exclude key pattern list
• relates to: OAK-4906 Lucene: Support relative property based query by transforming the path

Sub-Tasks

• Refactor encoding logic in property index to utility class: Closed
• Provide callback support for newly inserted entries in unique index: Closed
• AsyncIndexInfoService - Method to detect change in indexer state: Closed
• Support non root index in ContentMirrorStoreStrategy: Closed
• IndexTracker should check diff on :status node to detect index updates: Closed
• Reindex handling with synchronous lucene property indexes: Closed
• Delete property index entries recursively in batches to avoid large transaction: Closed
• Synchronous nodetype lucene index support: Closed
• Lucene unique index should check path validity for uniqueness constraint: Closed