[
https://issues.apache.org/jira/browse/OAK-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978235#comment-15978235
]
Vikas Saurabh commented on OAK-6082:
------------------------------------
Lgtm too... I wonder, btw, if we should also check if nodetype is indeed
enabled?
Also, as Thomas was eluding to: maybe we can do lazy/delayed init list of
indices and then observe v/s peek into nodetype each time the list is required?
But, I guess than can definitely be done later, if required. Baiscally, if I'm
following the idea correctly: this service would be useful to see where do we
have indices while various kind of traversals (I can only remember IndexUpdate
atm). Query at each access can potentially get pretty expensive unless the
client code acts smartly (caches the results first).
> Service to determine index paths
> --------------------------------
>
> Key: OAK-6082
> URL: https://issues.apache.org/jira/browse/OAK-6082
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: indexing
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.8
>
> Attachments: OAK-6082-v1.patch
>
>
> It would be useful to have an {{IndexPathService}} which would provide
> # List of all index paths
> # Determine if oak:index node is present under given path
> The service would make use of nodetype index for {{oak:QueryIndexDefinition}}
> for determining index paths.
> This service can then be used to enable improvements like
> * listing report for all indexes (OAK-6080),
> * Reduce lookup for oak:index nodes
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
