[
https://issues.apache.org/jira/browse/SOLR-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032488#comment-18032488
]
Jan Høydahl commented on SOLR-17182:
------------------------------------
Hi [~ab]
Preparing for transition to logchange tooling next week I found some duplicate
Jira entries in the CHANGES.txt for this issue
{code:java}
Deprecation Removals
----------------------
* SOLR-17182: Remove `solr.useExitableDirectoryReader` property. (Andrzej
Bialecki)
Other Changes
---------------------
* SOLR-17182: Remove `solr.useExitableDirectoryReader` property. Using
`ExitableDirectoryReader`
apparently has negligible impact on search performance so it's used now for
all queries regardless of
their query limits params. (Andrzej Bialecki) {code}
Please consolidate to one entry and commit to relevant branches
> Eliminate the need for 'solr.useExitableDirectoryReader' sysprop
> ----------------------------------------------------------------
>
> Key: SOLR-17182
> URL: https://issues.apache.org/jira/browse/SOLR-17182
> Project: Solr
> Issue Type: Sub-task
> Components: Query Limits
> Affects Versions: 9.9
> Reporter: Chris M. Hostetter
> Assignee: Andrzej Bialecki
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.0
>
> Attachments: gen-random-csv.pl, run-queries.sh
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> As the {{QueryLimit}} functionality in Solr gets beefed up, and supports
> multiple types of limits, it would be nice if we could find a way to
> eliminate the need for the {{solr.useExitableDirectoryReader}} sysprop, and
> instead just have codepaths that use the underlying IndexReader (like
> faceting, spellcheck, etc...) automatically get a reader that enforces the
> limits if/when limits are in use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
