[
https://issues.apache.org/jira/browse/SOLR-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034118#comment-18034118
]
Andrzej Bialecki commented on SOLR-17182:
-----------------------------------------
This was intentional because I wanted to address both the fact that the sysprop
has been removed and people that have this setting in their env should not
expect it to work, as well as the fact that EDR is now used for all queries
which may change the query execution behavior in some edge cases.
[~janhoy] If it's causing problems with the logchange tools feel free to merge
it into a single entry.
> 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]
