You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Simon Willnauer (JIRA)" <ji...@apache.org> on 2014/03/12 21:32:46 UTC
[jira] [Resolved] (LUCENE-5519) Make queueDepth enforcing optional
in TopNSearcher
[ https://issues.apache.org/jira/browse/LUCENE-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Willnauer resolved LUCENE-5519.
-------------------------------------
Resolution: Fixed
> Make queueDepth enforcing optional in TopNSearcher
> --------------------------------------------------
>
> Key: LUCENE-5519
> URL: https://issues.apache.org/jira/browse/LUCENE-5519
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/FSTs
> Affects Versions: 4.7
> Reporter: Simon Willnauer
> Priority: Minor
> Fix For: 4.8, 5.0
>
> Attachments: LUCENE-5519.patch, LUCENE-5519.patch, LUCENE-5519.patch
>
>
> currently TopNSearcher enforces the maxQueueSize based on rejectedCount + topN. I have a usecase where I just simply don't know the exact limit and I am ok with a top N that is not 100% exact. Yet, if I don't specify the right upper limit for the queue size I get an assertion error when I run tests but the only workaround it to make the queue unbounded which looks odd while it would possibly work just fine. I think it's fair to add an option that just doesn't enforce the limit and if it shoudl be enforced we throw a real exception.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org