[jira] [Commented] (OAK-2263) Avoid unnecessary reads on index lookup
[ https://issues.apache.org/jira/browse/OAK-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173780#comment-15173780 ] Chetan Mehrotra commented on OAK-2263: -- With OAK-2679 this aspect is very much addressed. Repeated read for property definition node is avoided > Avoid unnecessary reads on index lookup > --- > > Key: OAK-2263 > URL: https://issues.apache.org/jira/browse/OAK-2263 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > > The PropertyIndex looks up the matching index definitions multiple times. > This means each time all definitions are read to find out which one matches > the given property restriction. AFAICS this happens at least six times. The > first two times when the cost is calculated: 1) check if the property is > indexed and 2) calculate the cost. The next four times when the query is > executed: 3) check if the property is indexed, 4) calculate the cost, 5) > check if the property is indexed, 6) lookup index to create cursor for query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-2263) Avoid unnecessary reads on index lookup
[ https://issues.apache.org/jira/browse/OAK-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14362910#comment-14362910 ] Marcel Reutegger commented on OAK-2263: --- Already reported as OAK-1273. Resolving this issue as a duplicate. Avoid unnecessary reads on index lookup --- Key: OAK-2263 URL: https://issues.apache.org/jira/browse/OAK-2263 Project: Jackrabbit Oak Issue Type: Improvement Components: core Reporter: Marcel Reutegger Assignee: Marcel Reutegger Priority: Minor The PropertyIndex looks up the matching index definitions multiple times. This means each time all definitions are read to find out which one matches the given property restriction. AFAICS this happens at least six times. The first two times when the cost is calculated: 1) check if the property is indexed and 2) calculate the cost. The next four times when the query is executed: 3) check if the property is indexed, 4) calculate the cost, 5) check if the property is indexed, 6) lookup index to create cursor for query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
