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 2014/11/29 17:15:12 UTC
[jira] [Resolved] (OAK-2298) LuceneIndex should provide correct
cost based on index size
[ https://issues.apache.org/jira/browse/OAK-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved OAK-2298.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.2)
1.1.3
1.0.9
For now implemented following support
* {{costPerEntry}} - Defaults to 1.0
* {{costPerExecution}} - Defaults to 1.0
* {{termCount}} - Defaults to 1000. This would be used for query only involving {{PropertyRestriction}}. The default value would not be applicable for {{FulltextSearch}}. However if its set explicitly then it would apply for both
* trunk - http://svn.apache.org/r1642031
* 1.0 - http://svn.apache.org/r1642116
> LuceneIndex should provide correct cost based on index size
> -----------------------------------------------------------
>
> Key: OAK-2298
> URL: https://issues.apache.org/jira/browse/OAK-2298
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: oak-lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.0.9, 1.1.3
>
>
> {{LuceneIndex}} currently provides a hardcoded cost of 10. This causes issue if on same system both old {{LuceneIndex}} and newer {{LucenePropertyIndex}} are configured as former would always win
> To make comparison fair it should report accurate cost based on num of docs in index. Given that {{LuceneIndex}} is only used for fulltext queries it does not have to compete with other property index, it should be safe to provide accurate cost
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)