[
https://issues.apache.org/jira/browse/SOLR-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028716#comment-18028716
]
ASF subversion and git services commented on SOLR-17182:
--------------------------------------------------------
Commit 29c96eb55db987e4091d73ac8cf26e92bbf1fc94 in solr's branch
refs/heads/main from Andrzej Bialecki
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=29c96eb55db ]
SOLR-17182: Part 1: add ExitableDirectoryReader benchmark. (#3739)
Refactor CallerSpecificQueryLimit to create a reusable CallerMatcher.
> 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
> Attachments: gen-random-csv.pl, run-queries.sh
>
> Time Spent: 1h 40m
> 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]
