You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/05/05 08:57:12 UTC

[jira] [Updated] (OAK-4144) Expose PropertyIndex stats

     [ https://issues.apache.org/jira/browse/OAK-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated OAK-4144:
---------------------------------
           Labels:   (was: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4)
    Fix Version/s: 1.4.3
                   1.2.15
                   1.0.31

Merged to branches
* 1.0 - [1742380|http://svn.apache.org/r1742380]
* 1.2 - [1742381|http://svn.apache.org/r1742381]
* 1.4 - [1742382|http://svn.apache.org/r1742382]

> Expose PropertyIndex stats 
> ---------------------------
>
>                 Key: OAK-4144
>                 URL: https://issues.apache.org/jira/browse/OAK-4144
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: query
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.6, 1.5.1, 1.0.31, 1.2.15, 1.4.3
>
>         Attachments: OAK-4144-v1.patch, property-index-stats.png
>
>
> It would be good to have some stats exposed around property index specially for those based on ContentMirrorStoreStrategy
> The index structure is like
> {noformat}
> oak:index
>   + status
>     + :index
>       + PASS
>         + etc
>           + workflow
>             + instance
>               + a
>                 - match = true
>       + FAIL
>         + etc
>           + workflow
>             + instance
>               + b
>                 - match = true
> {noformat}
> # 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)