[OAK-6353] Use Document order traversal for reindexing performed on DocumentNodeStore setups

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.14, 1.8.0
• Component/s: run
• Epic Link: Index Tooling 1.8
• Sprint: L16
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 15/Jun/17 12:38
• Updated: 02/Aug/19 04:01
• Resolved: 18/Dec/17 06:42

Description

tmueller suggested here that document order traversal can be faster compared to current mode of path based traversal. Initial test indicate that such a traversal can be order of magnitude faster.

So this task is meant to implement such an approach and see if it can be a viable indexing mode used for DocumentNodeStore based setups

Issue Links

• is blocked by: OAK-6613 Provide list of all bundled nodes within a given DocumentNodeState
• is related to: OAK-7123 ChildNodeStateProvider does not return all immediate children
• is related to: OAK-7074 Ensure that all Documents are read with document order traversal indexing
• is related to: OAK-7115 Store NodeState json in bytes when storing in in-memory queue
• is related to: OAK-8525 Document --doc-traversal-mode for oak-run based indexing
• relates to: OAK-6246 Support for out of band indexing with read only access to NodeStore
• relates to: OAK-7079 Enable oak-run indexing to connect to secondary node in Mongo replica set

Sub-Tasks

• Blob serializer to serialize BlobStoreBlob: Closed
• Enable support for custom types in ExternalSort: Closed
• IndexDefinition should provides names of indexed relative node names: Closed
• Expose readOnly status for MongoDocumentStore: Closed