[
https://issues.apache.org/jira/browse/OAK-9781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541610#comment-17541610
]
Dan Klco commented on OAK-9781:
-------------------------------
Thanks for the catch on the inverted logic!
I would _assume_ the same, since you can already constrain the result size and
the code is pretty aggressive about enforcing this constraint however, I
wouldn't _think_ this would be an issue.
I'll work on some test cases, since the code is already sorting by descending
count, I wouldn't _think_ we need another parameter, we could just fix this,
but I'm open to discussion on this.
> Lucene Index MBean getFieldTerms Excludes Results for Unique Fields
> -------------------------------------------------------------------
>
> Key: OAK-9781
> URL: https://issues.apache.org/jira/browse/OAK-9781
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.8.0
> Reporter: Dan Klco
> Priority: Minor
> Fix For: 1.44.0
>
>
> The getFieldTerms method in the Lucene Index MBean only includes terms with >
> 1 documents. This means that terms with unique or very well distributed
> values such as UUIDs, paths or even file sizes will return few or no results
> from this method.
> Instead, this should only exclude terms where there are no associated
> documents.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
