Details
Description
It would be good to have some stats exposed around property index specially for those based on ContentMirrorStoreStrategy
The index structure is like
oak:index + status + :index + PASS + etc + workflow + instance + a - match = true + FAIL + etc + workflow + instance + b - match = true
- List of values being indexed - Like FAIL, PASS etc or count
- Path of content being index - Say path upto 3 levels where given property exists. For above case it would be /etc/workflow/instance
#2 can be used to come up with right values for includedPaths OAK-3263. Having includedPath has benefits in terms of
- Faster reindexing times
- Make commits faster - Each property index currently contributes one IndexEditor and this editor would participate in each commit. If number of property indexes are high then it would lead to slow down in commit rates (OAK-1273). So having includedPath would allow reduction in number of editors that participate in a commit