[
https://issues.apache.org/jira/browse/OAK-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608351#comment-14608351
]
Alex Parvulescu commented on OAK-3011:
--------------------------------------
bq. its not meant to be actually implemented by others
But 'others' in OSGi terms is also _oak-lucene_. I'm quite confused here.
_IndexPlan_ is an interface where a _Builder_ class is also defined, so you
could in theory implement your own, but it is simpler to use the provided
builder. Now why would you expose the interface if no one is supposed to
implement it? and how will marking it with _ProviderType_ affect _oak-lucene_?
> Add name of lucene-property index to cost debug log
> ---------------------------------------------------
>
> Key: OAK-3011
> URL: https://issues.apache.org/jira/browse/OAK-3011
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene, query
> Reporter: Alex Parvulescu
> Fix For: 1.2.3, 1.3.2
>
> Attachments: OAK-3011-v2.patch, OAK-3011.patch
>
>
> Currently the cost debug log only contains the type and the cost, but if
> there are multiple lucene-property indexes, there's no way of knowing which
> index has what cost so it would be really nice to have the index name
> included with the cost output.
> Now:
> {code}
> org.apache.jackrabbit.oak.query.QueryImpl cost for lucene-property is 1.5
> {code}
> Nice to have:
> {code}
> org.apache.jackrabbit.oak.query.QueryImpl cost for lucene-property [name] is
> 1.5
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
