Description
With Document Traversal based indexing we have implemented a newer indexing logic. To validate that index produced by it is is same as one done by existing indexing flow we need to implement a script which can enable comparing the index content logically
This was recently discussed on lucene mailing list [1] and suggestion there was it can be done by un-inverting the index. So to enable that we need to implement a script which can
- Open a Lucene index
- Map the Lucene Document to path of node
- For each document determine what all fields are associated with it (stored and non stored)
- Dump this content in file sorted by path and for each line field name sorted by name
Then such dumps can be generated for old and new index and compared via simple text diff
Attachments
Issue Links
- is related to
-
OAK-7123 ChildNodeStateProvider does not return all immediate children
-
- Closed
-