[jira] [Reopened] (OAK-6735) Lucene Index: improved cost estimation by using document count per field

["Thomas Mueller (JIRA)" <ji...@apache.org>]

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

Thomas Mueller reopened OAK-6735:
---------------------------------

I see "jcr:title" is hardcoded, that doesn't look right. What is the reason for this? Could we at least make this configurable (e.g. using a system property)?

Also, it looks like properties with name ending with "_facet" have a special meaning. What is a customer uses such property names... don't we have a good escape mechanism (for example using the ":" prefix)?

> Lucene Index: improved cost estimation by using document count per field
> ------------------------------------------------------------------------
>
>                 Key: OAK-6735
>                 URL: https://issues.apache.org/jira/browse/OAK-6735
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene, query
>    Affects Versions: 1.7.4
>            Reporter: Thomas Mueller
>            Assignee: Vikas Saurabh
>            Priority: Major
>             Fix For: 1.8, 1.7.11
>
>         Attachments: IndexReadPattern.txt, LuceneIndexReadPattern.java, OAK-6735.patch
>
>
> The cost estimation of the Lucene index is somewhat inaccurate because (by default) it just used the number of documents in the index (as of Oak 1.7.4 by default, due to OAK-6333).
> Instead, it should use the number of documents for the given fields (the minimum, if there are multiple fields with restrictions). 
> Plus divided by the number of restrictions (as we do now already).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)