[
https://issues.apache.org/jira/browse/LUCENE-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847400#comment-16847400
]
Adrien Grand commented on LUCENE-8808:
--------------------------------------
In general I'm reluctant to adding more configuration options. It increases the
API surface area, which in turn makes Lucene harder to use. My gut feeling
right now is that this new setting would not help enough to warrant the
introduction of a new option?
> Introduce Optional Cap on Number Of Threads Per Query
> -----------------------------------------------------
>
> Key: LUCENE-8808
> URL: https://issues.apache.org/jira/browse/LUCENE-8808
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Atri Sharma
> Priority: Major
>
> With the presence of https://issues.apache.org/jira/browse/LUCENE-8757 , a
> natural progression is to allow advanced users to specify a cap on the number
> of threads a query can use. This is especially useful for long polled
> IndexSearcher instances, where the same instance is used to fire queries for
> multiple runs and there are multiple concurrent IndexSearcher instances on
> the same node.
>
> This will be an optional parameter and local only to the IndexSearcher
> instance being configured during construction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
