[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2019-11-19 Thread Thomas Mueller (Jira)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-3219: Fix Version/s: (was: 1.22.0) > Lucene IndexPlanner should also account for number of property

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2019-06-04 Thread Davide Giannella (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3219: -- Fix Version/s: (was: 1.14.0) > Lucene IndexPlanner should also account for number of

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2019-06-04 Thread Davide Giannella (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3219: -- Fix Version/s: 1.16.0 > Lucene IndexPlanner should also account for number of property

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2019-04-09 Thread Davide Giannella (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3219: -- Fix Version/s: 1.14.0 > Lucene IndexPlanner should also account for number of property

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2019-04-09 Thread Davide Giannella (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3219: -- Fix Version/s: (was: 1.12.0) > Lucene IndexPlanner should also account for number of

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2019-01-09 Thread Davide Giannella (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3219: -- Fix Version/s: (was: 1.10.0) > Lucene IndexPlanner should also account for number of

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2019-01-09 Thread Davide Giannella (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3219: -- Fix Version/s: 1.12 > Lucene IndexPlanner should also account for number of property constraints

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2016-12-07 Thread Daniel Hasler (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Hasler updated OAK-3219: --- Fix Version/s: (was: 1.6) 1.8 > Lucene IndexPlanner should also account for

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2016-11-17 Thread Thomas Mueller (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-3219: Description: Currently the cost returned by Lucene index is a function of number of indexed

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2016-11-10 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-3219: Assignee: Thomas Mueller (was: Chetan Mehrotra) > Lucene IndexPlanner should also account for number of property

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2016-01-20 Thread Chetan Mehrotra (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-3219: - Fix Version/s: (was: 1.4) 1.6 > Lucene IndexPlanner should also account for

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2015-11-16 Thread Chetan Mehrotra (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-3219: - Fix Version/s: (was: 1.3.11) 1.4 > Lucene IndexPlanner should also account

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2015-11-09 Thread Davide Giannella (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3219: -- Fix Version/s: (was: 1.3.10) 1.3.11 > Lucene IndexPlanner should also

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2015-09-27 Thread Amit Jain (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-3219: --- Fix Version/s: (was: 1.3.7) 1.3.8 > Lucene IndexPlanner should also account for number

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2015-08-25 Thread Michael Marth (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-3219: --- Fix Version/s: (was: 1.3.6) 1.3.7 Lucene IndexPlanner should also account for

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2015-08-20 Thread Michael Marth (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-3219: --- Labels: performance (was: ) Lucene IndexPlanner should also account for number of property

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2015-08-12 Thread Chetan Mehrotra (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-3219: - Description: Currently the cost returned by Lucene index is a function of number of indexed

[jira] [Updated] (OAK-3219) Lucene IndexPlanner should also account for number of property constraints evaluated while giving cost estimation

2015-08-12 Thread Chetan Mehrotra (JIRA)
[ https://issues.apache.org/jira/browse/OAK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-3219: - Description: Currently the cost returned by Lucene index is a function of number of indexed