[jira] [Updated] (OAK-2263) Avoid unnecessary reads on index lookup

2015-03-16 Thread Marcel Reutegger (JIRA)

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

Marcel Reutegger updated OAK-2263:
--
Fix Version/s: (was: 1.4)

 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] [Updated] (OAK-2263) Avoid unnecessary reads on index lookup

2015-03-09 Thread Marcel Reutegger (JIRA)

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

Marcel Reutegger updated OAK-2263:
--
Fix Version/s: (was: 1.1.8)
   1.4

 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
 Fix For: 1.4


 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] [Updated] (OAK-2263) Avoid unnecessary reads on index lookup

2015-02-18 Thread Marcel Reutegger (JIRA)

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

Marcel Reutegger updated OAK-2263:
--
Fix Version/s: (was: 1.1.7)
   1.1.8

 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
 Fix For: 1.1.8


 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] [Updated] (OAK-2263) Avoid unnecessary reads on index lookup

2015-02-04 Thread Marcel Reutegger (JIRA)

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

Marcel Reutegger updated OAK-2263:
--
Fix Version/s: (was: 1.1.6)
   1.1.7

 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
 Fix For: 1.1.7


 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] [Updated] (OAK-2263) Avoid unnecessary reads on index lookup

2015-01-21 Thread Michael Marth (JIRA)

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

Michael Marth updated OAK-2263:
---
Fix Version/s: 1.1.6

 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
 Fix For: 1.1.6


 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)