[
https://issues.apache.org/jira/browse/OAK-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194824#comment-16194824
]
Vikas Saurabh commented on OAK-6735:
------------------------------------
bq. I would be in favour of supporting customer defined selectivity per
property. See also:
Quick question: do you mean that:
* we generate some statistics which end-user can
scale-up/down/completely-override according to domain knowledge (I don't feel
nice about complete over-ride though), OR
* end user has some way to force refresh stored statistics (like {{ANALYZE}}
command in links posted above), OR
* no auto stats generation. End user can give some inputs in index def to give
some hint for cost estimation though?
> 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
> Fix For: 1.8
>
>
> 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)
